Triple
T14250612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Man |
E353249
|
entity |
| Predicate | affiliationRole |
P13957
|
FINISHED |
| Object | founding member of the Avengers |
—
|
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: founding member of the Avengers | Statement: [Iron Man, affiliationRole, founding member of the Avengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliationRole Context triple: [Iron Man, affiliationRole, founding member of the Avengers]
-
A.
hasOrganizationalRole
chosen
Indicates that an entity holds a specific role, position, or function within an organization.
-
B.
awardingOrganizationRole
Indicates that an entity holds a specific role or capacity within the organization that grants or confers an award.
-
C.
holderAffiliation
Indicates that a holder (such as a person or organization) is affiliated with, or belongs to, a particular group, institution, or entity.
-
D.
subjectAffiliation
Indicates that a subject is formally associated or connected with a particular organization, group, or institution.
-
E.
stateAssociationAffiliation
Indicates a formal relationship in which an entity is associated or affiliated with a particular state or state-level organization.
- F. None of above.
Provenance (3 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6296f9d0819086f62f525d07eb12 |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.