Triple
T4145239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EDVAC |
E89365
|
entity |
| Predicate | logicType |
P54594
|
FINISHED |
| Object | binary |
—
|
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: binary | Statement: [EDVAC, logicType, binary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicType Context triple: [EDVAC, logicType, binary]
-
A.
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.
-
B.
logicSystem
Indicates a relationship where an entity is associated with, defined within, or governed by a particular logical framework or system of formal reasoning.
-
C.
logicalTrait
Indicates that an entity possesses a characteristic, behavior, or quality related to logical reasoning or structured thinking.
-
D.
logicalPolarity
Indicates that the truth value of a statement is affirmed (positive) or denied (negative) relative to some logical context.
-
E.
logicLevelDetermines
Indicates that the specific logic level of one entity determines or dictates the resulting state, behavior, or outcome of 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af033d94888190b34349e355b874ef |
completed | March 9, 2026, 5:28 p.m. |
Created at: March 9, 2026, 3:43 p.m.