Triple
T397195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western European Union |
E9208
|
entity |
| Predicate | dissolutionCompleted |
P133
|
FINISHED |
| Object | 30 June 2011 |
—
|
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: 30 June 2011 | Statement: [Western European Union, dissolutionCompleted, 30 June 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolutionCompleted Context triple: [Western European Union, dissolutionCompleted, 30 June 2011]
-
A.
dissolved
Indicates that one substance has been mixed into another so thoroughly that it forms a uniform solution and is no longer distinguishable as a separate phase.
-
B.
dissolvedOrAbolished
chosen
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
C.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
conversionCompleted
Indicates that a previously initiated conversion process has finished successfully.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8bcf708190b62e15806159ceb1 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.