Triple
T11092241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TMB 7000 series |
E262283
|
entity |
| Predicate | hasMultipleUnitsOperation |
P66171
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TMB 7000 series, hasMultipleUnitsOperation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleUnitsOperation Context triple: [TMB 7000 series, hasMultipleUnitsOperation, yes]
-
A.
hasMultipleUnitControl
chosen
Indicates that a single controller or agent is able to direct, manage, or operate more than one unit simultaneously.
-
B.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
C.
canOperateInMultipleWith
Indicates that an entity is capable of functioning or being used concurrently within multiple instances, contexts, or configurations of another entity.
-
D.
multipleUnit
Indicates that an entity is composed of or associated with more than one unit of the same type.
-
E.
canOperateInMultiple
Indicates that an entity is capable of functioning or being used across more than one context, environment, or mode.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799ec6564819097624195d0cd9093 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.