Triple
T677521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic states |
E13110
|
entity |
| Predicate | independenceWave |
P17961
|
FINISHED |
| Object | late 1980s and early 1990s |
—
|
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: late 1980s and early 1990s | Statement: [Baltic states, independenceWave, late 1980s and early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: independenceWave Context triple: [Baltic states, independenceWave, late 1980s and early 1990s]
-
A.
involvedIndependenceMovement
Indicates that an entity actively participated in or contributed to an independence movement seeking political or national self-determination.
-
B.
independenceRestored
Indicates that a previously dependent or controlled entity has regained its autonomy or self-governance.
-
C.
resultOfIndependence
Indicates that something exists or occurs as a consequence or outcome of an independence event or process.
-
D.
independenceFrom
Indicates that one entity is not controlled, governed, or significantly influenced by another entity.
-
E.
independenceRecognized
Indicates that one entity formally acknowledges another entity’s status as independent and self-governing.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a04c89148190b6330e86697bb37b |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1bbd0c81909cfbec30bd17bde7 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49ebf33c481909949526cb8f223dd |
completed | March 1, 2026, 8:17 p.m. |
Created at: March 1, 2026, 7:36 p.m.