Triple
T18367643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpine F1 Team |
E440089
|
entity |
| Predicate | mainFactoryFunction |
P18495
|
FINISHED |
| Object | chassis design and assembly |
—
|
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: chassis design and assembly | Statement: [Alpine F1 Team, mainFactoryFunction, chassis design and assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainFactoryFunction Context triple: [Alpine F1 Team, mainFactoryFunction, chassis design and assembly]
-
A.
mainFunctionAtCreation
Indicates the primary function or role an entity was originally designed or intended to perform at the time of its creation.
-
B.
mainCreator
Indicates that an entity is the primary or most responsible creator of another entity (such as a work, product, or artifact).
-
C.
mainFunctions
chosen
Indicates that the subject serves as the primary or central functional component or role for the object.
-
D.
mainSingle
Indicates that an entity is the primary or sole main instance among a set of related entities.
-
E.
mainImplementer
Indicates that an entity is the primary party responsible for carrying out, developing, or executing a specified action, project, or implementation.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5174f5f448190a1fc67d3039aadd9 |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:38 a.m.