Triple
T21837130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M928 |
E539147
|
entity |
| Predicate | crewCab |
P145510
|
FINISHED |
| Object | 2-door cab |
—
|
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: 2-door cab | Statement: [M928, crewCab, 2-door cab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewCab Context triple: [M928, crewCab, 2-door cab]
-
A.
crewSystem
Indicates a relationship where a system is specifically designed for, assigned to, or operated by a particular crew.
-
B.
crewMate
Indicates that two entities are members of the same crew or team, sharing a common group affiliation or working together in a joint capacity.
-
C.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
-
D.
crewChief
Indicates that one person serves as the lead or supervising crew chief responsible for directing and managing another person or group in an operational context.
-
E.
hasCrewCompartmentMaterial
Indicates that an entity’s crew compartment is made of, or incorporates, a specified material.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a890208190a902184e60194e1c |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c187bc548190b4ca13150f6bae38 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 6:55 p.m.