Triple
T24048324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EC250 / SMILE |
E595582
|
entity |
| Predicate | multipleUnitConfiguration |
P154664
|
FINISHED |
| Object | fixed formation |
—
|
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: fixed formation | Statement: [EC250 / SMILE, multipleUnitConfiguration, fixed formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multipleUnitConfiguration Context triple: [EC250 / SMILE, multipleUnitConfiguration, fixed formation]
-
A.
multipleUnit
Indicates that an entity is composed of or associated with more than one unit of the same type.
-
B.
typicalUnitConfiguration
Indicates the standard or commonly used arrangement, composition, or setup of a unit in a given context.
-
C.
configurationUnit
Indicates that one entity serves as a configuration unit or configurable component used to define or adjust the setup or behavior of another entity.
-
D.
hasMultipleUnitControl
Indicates that a single controller or agent is able to direct, manage, or operate more than one unit simultaneously.
-
E.
managementUnitOf
Indicates that one entity serves as the administrative or managerial unit responsible for overseeing or controlling another entity.
- F. None of above. chosen
Provenance (4 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9cedaa08190bf54857de1b312ed |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:18 p.m.