Triple
T2225730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Union Day |
E48642
|
entity |
| Predicate | officialStatusSince |
P19818
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Great Union Day, officialStatusSince, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialStatusSince Context triple: [Great Union Day, officialStatusSince, 1990]
-
A.
coOfficialStatusIn
Indicates that two or more entities share the same official status within a specified context, such as a jurisdiction, organization, or system.
-
B.
officialStatusWithTeam
Indicates that an entity holds or has held an official role, position, or status in relation to a specific team.
-
C.
agencyStatus
Indicates the current operational or legal condition under which an agency or agent is functioning (e.g., active, inactive, suspended, or terminated).
-
D.
currentStatusSince
chosen
Indicates the point in time since which an entity has held its current status or state.
-
E.
recognizedSince
Indicates that one entity has formally acknowledged, accepted, or identified another entity as valid or legitimate starting from a specific point in time.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc03ffcbc8190a27e32af831c7be5 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.