Triple
T36115276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota GR Supra GT4 |
E1044600
|
entity |
| Predicate | aeroPackage |
P184692
|
FINISHED |
| Object | front splitter |
—
|
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: front splitter | Statement: [Toyota GR Supra GT4, aeroPackage, front splitter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aeroPackage Context triple: [Toyota GR Supra GT4, aeroPackage, front splitter]
-
A.
airSupport
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
-
B.
airframer
Indicates a relationship where a company designs, manufactures, or assembles aircraft as its primary aerospace activity.
-
C.
airTransportableBy
Indicates that something can be transported or carried by air using a specific aircraft or air transport method.
-
D.
hasCargoAirline
Indicates that one entity operates as a cargo airline for, or provides cargo air transport services to, another entity.
-
E.
airframe
Indicates that an entity is the structural framework or body of an aircraft associated with another entity (such as a specific model, component, or system).
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b3e0f1c88190985feab6cee8b05e |
completed | May 3, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:08 p.m.