Triple
T10735203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GP40PH-2 |
E253177
|
entity |
| Predicate | hasMultipleUnitCapability |
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: [GP40PH-2, hasMultipleUnitCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleUnitCapability Context triple: [GP40PH-2, hasMultipleUnitCapability, 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.
multipleUnit
Indicates that an entity is composed of or associated with more than one unit of the same type.
-
D.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
E.
hasMultipleWorking
Indicates that an entity is associated with more than one working instance, role, or configuration simultaneously.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71021cccc8190ba2d3bbd7d50e2a7 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.