Triple
T35811298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkey–Soviet Union border |
E1035235
|
entity |
| Predicate | hasSectionWithSuccessorState |
P80604
|
FINISHED |
| Object | Armenia |
—
|
NE NERFINISHED |
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: Armenia | Statement: [Turkey–Soviet Union border, hasSectionWithSuccessorState, Armenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSectionWithSuccessorState Context triple: [Turkey–Soviet Union border, hasSectionWithSuccessorState, Armenia]
-
A.
hasSuccessors
Indicates that an entity is followed or replaced by one or more subsequent entities in a sequence, process, or lineage.
-
B.
hasSuccessorSegment
chosen
Indicates that one segment directly follows another segment in a sequence or ordered structure.
-
C.
hasCurrentSuccessor
Indicates that one entity is the immediate next or following entity in a current, ordered sequence or progression of another entity.
-
D.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
E.
hasOnlineSuccessor
Indicates that one entity is the direct online or digital successor of another, typically replacing or continuing its function in an online context.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
Created at: May 3, 2026, 4:06 p.m.