Triple
T23040036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM Firebird I |
E573707
|
entity |
| Predicate | hasRoadLegalStatus |
P2250
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [GM Firebird I, hasRoadLegalStatus, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadLegalStatus Context triple: [GM Firebird I, hasRoadLegalStatus, no]
-
A.
hasLegalStatus
chosen
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
B.
hasRoadAuthority
Indicates that one entity holds official control, responsibility, or decision-making power over a road or road network in relation to another entity.
-
C.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
D.
hasLegalStatusOver
Indicates that one entity holds a recognized legal authority, jurisdiction, or standing in relation to another entity.
-
E.
driverStatus
Indicates the current operational or availability state of a driver in relation to their driving duties.
- F. None of above.
Provenance (3 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18512df708190a6892e743a289c74 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:53 p.m.