Triple
T8233672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiger UHT |
E192352
|
entity |
| Predicate | crewLayout |
P80991
|
FINISHED |
| Object | tandem seating |
—
|
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: tandem seating | Statement: [Tiger UHT, crewLayout, tandem seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewLayout Context triple: [Tiger UHT, crewLayout, tandem seating]
-
A.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
-
B.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
-
C.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
-
D.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
E.
crewLocation
Indicates that a crew is located at, assigned to, or present in a specific place or environment.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782792a48190a34b0abfcc92064b |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb3d6c34708190a987d68529cbb0b3 |
completed | March 31, 2026, 3:20 a.m. |
Created at: March 30, 2026, 5:46 p.m.