Triple
T35809190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Angle |
E1035181
|
entity |
| Predicate | memberRoleCharlieHaas |
P194438
|
FINISHED |
| Object | protégé of Kurt Angle |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: protégé of Kurt Angle | Statement: [Team Angle, memberRoleCharlieHaas, protégé of Kurt Angle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberRoleCharlieHaas Context triple: [Team Angle, memberRoleCharlieHaas, protégé of Kurt Angle]
-
A.
hasHumanCharacterRole
Indicates that an entity is assigned a role or function specifically associated with a human character within a context such as a story, performance, or representation.
-
B.
mainActorForCharacter_CharlieCrews
Indicates that the referenced person is the primary actor who portrays the character Charlie Crews.
-
C.
roleOfCharliePace
Indicates that the specified entity is the role or character portrayed by Charlie Pace.
-
D.
roleInHaroldAndKumarSeries
Indicates that an entity portrays a character in the Harold and Kumar film series.
-
E.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: May 3, 2026, 4:06 p.m.