Triple
T6851040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula One Management |
E158013
|
entity |
| Predicate | roleRelativeToFIA |
P72616
|
FINISHED |
| Object | commercial rights holder |
—
|
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: commercial rights holder | Statement: [Formula One Management, roleRelativeToFIA, commercial rights holder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleRelativeToFIA Context triple: [Formula One Management, roleRelativeToFIA, commercial rights holder]
-
A.
roleAtD.C.United
Indicates that an entity holds or held a specific role or position within the D.C. United soccer organization.
-
B.
appointedRelative
Indicates that one entity has formally assigned or designated another entity, who is a relative, to a specific role, position, or responsibility.
-
C.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
D.
actsOnBehalfOf
Indicates that one entity performs actions or makes decisions as a representative or proxy for another entity.
-
E.
appointedOnBehalfOf
Indicates that an appointment or designation is made by one party acting in representation of, or for the benefit of, another party.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84c45708190918adfc028252400 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:20 p.m.