Triple
T27687759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innocenti |
E698076
|
entity |
| Predicate | usedEngineFrom |
P4673
|
FINISHED |
| Object | BMC A-series engine |
—
|
NE NERFINISHED |
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: BMC A-series engine | Statement: [Innocenti, usedEngineFrom, BMC A-series engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedEngineFrom Context triple: [Innocenti, usedEngineFrom, BMC A-series engine]
-
A.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
B.
originatesFromEngine
Indicates that something has its source, cause, or production in a particular engine.
-
C.
usedEquipmentFrom
chosen
Indicates that one entity has utilized or operated equipment that originated from or was provided by another entity.
-
D.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
E.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63574d2388190839cd1061e3c9074 |
completed | May 2, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:50 p.m.