Triple
T10543101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isuzu Elf |
E248744
|
entity |
| Predicate | isInProduction |
P87831
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Isuzu Elf, isInProduction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInProduction Context triple: [Isuzu Elf, isInProduction, true]
-
A.
isProductionReady
Indicates that something has met all necessary quality, stability, and performance criteria to be safely deployed and used in a live production environment.
-
B.
productionEnvironment
chosen
Indicates that something is part of, deployed to, or operating within a live production environment as opposed to a test or development setting.
-
C.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
-
D.
hasProductionStatus
Indicates the current stage or condition of an entity’s production process (e.g., planned, in progress, completed, or discontinued).
-
E.
performedInProduction
Indicates that an entity (such as a person or group) took part as a performer in a specific production or performance event.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5190f46d08190a92b1191881ffb92 |
completed | April 7, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:32 p.m.