Triple
T26451692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyclone V |
E665366
|
entity |
| Predicate | logicElementRange |
P28992
|
FINISHED |
| Object | 25000 to 301000 logic elements (approximate) |
—
|
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: 25000 to 301000 logic elements (approximate) | Statement: [Cyclone V, logicElementRange, 25000 to 301000 logic elements (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicElementRange Context triple: [Cyclone V, logicElementRange, 25000 to 301000 logic elements (approximate)]
-
A.
logicCapacityRange
Indicates the range of logical processing or reasoning capacity that an entity can handle or support.
-
B.
rangeOf
chosen
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
C.
logicElementType
Indicates that one entity is classified as a specific type or category of logical element in relation to another.
-
D.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
coreRange
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 12:06 a.m.