Triple
T26333724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyclone III |
E662461
|
entity |
| Predicate | logicElementType |
P160568
|
FINISHED |
| Object | Adaptive Logic Module |
—
|
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: Adaptive Logic Module | Statement: [Cyclone III, logicElementType, Adaptive Logic Module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicElementType Context triple: [Cyclone III, logicElementType, Adaptive Logic Module]
-
A.
logicType
Indicates the specific kind or category of logical system, rule, or reasoning framework that an entity or statement belongs to.
-
B.
logicalType
Indicates that one entity is classified as a logical type or category used to define or constrain the logical behavior or interpretation of another entity.
-
C.
logicFunction
Indicates a relationship where one entity serves as a logical function or operator that determines the truth value or output based on given inputs or conditions involving another entity.
-
D.
logicalTrait
Indicates that an entity possesses a characteristic, behavior, or quality related to logical reasoning or structured thinking.
-
E.
circuitType
Indicates the specific kind or category of electrical circuit associated with an 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f6b1cac8190acae634753161983 |
completed | May 2, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 10:35 p.m.