Triple
T18671299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equipe Unifiée de l’ex-URSS |
E456481
|
entity |
| Predicate | hasNoSingleNationState |
P132218
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Equipe Unifiée de l’ex-URSS, hasNoSingleNationState, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoSingleNationState Context triple: [Equipe Unifiée de l’ex-URSS, hasNoSingleNationState, true]
-
A.
hasSovereignState
Indicates that one entity is the sovereign state that has ultimate authority or jurisdiction over another entity.
-
B.
hasNotableNation
Indicates that an entity is significantly associated with or recognized for a particular nation.
-
C.
hasNoSingleTreaty
Indicates that there is no single, unified treaty governing the relationship between the entities, implying multiple or fragmented agreements instead.
-
D.
hasNoPermanentSettlements
Indicates that the subject does not maintain any long-term or stable inhabited locations.
-
E.
multiNationalState
Indicates a state whose population is composed of multiple distinct national or ethnic groups under a single political authority.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b21d2481908e1b8b583bfabb72 |
completed | April 19, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.