Triple
T33986889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamborghini Sesto Elemento |
E871435
|
entity |
| Predicate | exhaustMaterial |
P177991
|
FINISHED |
| Object | Inconel |
—
|
NE NERFINISHED |
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: Inconel | Statement: [Lamborghini Sesto Elemento, exhaustMaterial, Inconel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhaustMaterial Context triple: [Lamborghini Sesto Elemento, exhaustMaterial, Inconel]
-
A.
exhaustType
Indicates the specific kind or configuration of exhaust system associated with an entity.
-
B.
ejectaMaterial
Indicates that one entity consists of or represents material that has been expelled or thrown out from another entity, typically by an energetic event such as an impact or explosion.
-
C.
exhaustNote
Indicates that one entity serves as an explanatory or qualifying note that elaborates on, clarifies, or limits the scope of another entity.
-
D.
exhaustPosition
Indicates the spatial location or configuration of an exhaust outlet relative to the object it belongs to.
-
E.
exhaustDirection
Indicates the direction in which exhaust gases or emissions are released or discharged from a source.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:50 a.m.