Triple
T9712840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butane |
E235060
|
entity |
| Predicate | validatesAgainst |
P23074
|
FINISHED |
| Object | Ignition specification |
—
|
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: Ignition specification | Statement: [Butane, validatesAgainst, Ignition specification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validatesAgainst Context triple: [Butane, validatesAgainst, Ignition specification]
-
A.
conformsTo
Indicates that one entity complies with, follows, or is in accordance with a specified standard, specification, rule, or guideline.
-
B.
hasValidity
Indicates that something possesses a period or condition during which it is considered legally, logically, or functionally acceptable or in force.
-
C.
supportsValidationOf
chosen
Indicates that one entity provides the mechanisms or conditions necessary for another entity to be checked or verified for correctness or compliance.
-
D.
validatorType
Indicates the specific kind or category of validator associated with an entity or operation.
-
E.
failsToConformTo
Indicates that one entity does not meet, match, or comply with the standards, rules, or expectations defined by another entity or specification.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e0705f8819095852263009c28c5 |
completed | April 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.