Triple
T28077988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saar Treaty |
E709596
|
entity |
| Predicate | effectiveDateOfReintegration |
P83226
|
FINISHED |
| Object | 1957-01-01 |
—
|
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: 1957-01-01 | Statement: [Saar Treaty, effectiveDateOfReintegration, 1957-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveDateOfReintegration Context triple: [Saar Treaty, effectiveDateOfReintegration, 1957-01-01]
-
A.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
B.
dateOfRehabilitation
Indicates the specific date on which a rehabilitation process, status, or measure for an entity was completed, granted, or took effect.
-
C.
reentryDate
Indicates the date on which an entity returns or is admitted again after a prior departure, exit, or release.
-
D.
effectivePeriodStart
chosen
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
E.
recoveryDate
Indicates the date on which a recovery process or restoration of a prior state is completed or officially recorded.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 8:50 p.m.