Triple
T33045200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Williams Racing Cars |
E845574
|
entity |
| Predicate | hasChassisConstructorRole |
P196221
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Frank Williams Racing Cars, hasChassisConstructorRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChassisConstructorRole Context triple: [Frank Williams Racing Cars, hasChassisConstructorRole, yes]
-
A.
hasChassisType
Indicates that an entity is associated with or equipped with a specific type of chassis.
-
B.
chassisConstruction
Indicates how the chassis of an object is built or assembled, specifying the construction method or structural design used.
-
C.
usedChassisFor
Indicates that one entity employed or incorporated another entity’s chassis as the structural base or framework for its construction or operation.
-
D.
allowsChassisSupplier
Indicates that one entity grants permission or authorization for another entity to act as or use a specified chassis supplier.
-
E.
chassis
Indicates that one entity serves as the structural frame or supporting base (chassis) for another entity.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_69fe1639613c8190aaf1b4c8e2d861ba |
completed | May 8, 2026, 4:58 p.m. |
Created at: May 1, 2026, 1:24 a.m.