Triple
T36108847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constructors' Championship |
E1044435
|
entity |
| Predicate | hasNotableConstructor |
P44379
|
FINISHED |
| Object | Ferrari |
E104281
|
NE 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: Ferrari | Statement: [Constructors' Championship, hasNotableConstructor, Ferrari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableConstructor Context triple: [Constructors' Championship, hasNotableConstructor, Ferrari]
-
A.
notableConstructor
chosen
Indicates that an entity is a well-known or significant creator, builder, or originator of another entity.
-
B.
hasConstructor
Indicates that an entity defines or is associated with a specific constructor used to create or initialize instances of it.
-
C.
hasParameterlessConstructor
Indicates that an object, class, or type defines a constructor that takes no parameters.
-
D.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
E.
usesConstructor
Indicates that one entity creates or initializes another entity by invoking its constructor.
- F. None of above.
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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39340007f08190a53738807251cd14 |
completed | June 22, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.