Triple
T26618339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avengers Initiative |
E668126
|
entity |
| Predicate | notableRecruit |
P198566
|
FINISHED |
| Object | Tony Stark |
—
|
NE NERFINISHED |
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: Tony Stark | Statement: [Avengers Initiative, notableRecruit, Tony Stark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRecruit Context triple: [Avengers Initiative, notableRecruit, Tony Stark]
-
A.
notableStudent
Indicates that a person is a distinguished or particularly significant student of another individual or institution.
-
B.
notableJunior
Indicates that one entity is a younger or less senior counterpart who is notably associated with another, more senior entity.
-
C.
notableRookie
Indicates that an individual is recognized as an outstanding or especially noteworthy rookie within a particular field or context.
-
D.
notableRank
Indicates that an entity holds a distinguished or significant position or level within a ranking or hierarchy.
-
E.
notableManager
Indicates that an entity has, or is associated with, a manager who is particularly prominent, distinguished, or widely recognized.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69fef3cdea708190af41c1ff23b68f88 |
completed | May 9, 2026, 8:43 a.m. |
Created at: April 27, 2026, 2:19 a.m.