Triple
T21802469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pseudonode |
E538269
|
entity |
| Predicate | existsWhen |
P67472
|
FINISHED |
| Object | A DR or DIS is elected on the segment |
—
|
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: A DR or DIS is elected on the segment | Statement: [Pseudonode, existsWhen, A DR or DIS is elected on the segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existsWhen Context triple: [Pseudonode, existsWhen, A DR or DIS is elected on the segment]
-
A.
existsIf
chosen
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
-
B.
existsAs
Indicates that one entity has the same identity or manifestation as another, effectively asserting they are the same existing thing or state.
-
C.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
D.
existsOnlyAs
Indicates that the subject exists solely in a particular form, state, or context specified by the object, and not in any other.
-
E.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0780062688190a6c3a2a0364f0f77 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.