Triple
T35817111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria–Czechoslovakia border |
E1035393
|
entity |
| Predicate | borderedPoliticalBloc |
P200827
|
FINISHED |
| Object | Western Bloc |
—
|
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: Western Bloc | Statement: [Austria–Czechoslovakia border, borderedPoliticalBloc, Western Bloc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedPoliticalBloc Context triple: [Austria–Czechoslovakia border, borderedPoliticalBloc, Western Bloc]
-
A.
regionalBloc
Indicates that an entity is a member of, or associated with, a specific regional political or economic bloc.
-
B.
borderingPoliticalEntityType
Indicates that one political entity is adjacent to and shares a boundary with another political entity of a specified type.
-
C.
geopoliticalOrganization
Indicates that an entity functions as a political or governmental body associated with a specific geographic region or territory.
-
D.
OSCEMember
Indicates that an entity is a member of, or affiliated with, the OSC (Open Source Community or similarly named organization).
-
E.
borderingRepublic
Indicates that one republic shares a land or maritime border with another republic.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69ffb120b9988190b6361c69265033c0 |
completed | May 9, 2026, 10:11 p.m. |
Created at: May 3, 2026, 4:06 p.m.