Triple
T28077908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saar Statute |
E709594
|
entity |
| Predicate | legalEffectAfterReferendum |
P59658
|
FINISHED |
| Object | did not enter into force |
—
|
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: did not enter into force | Statement: [Saar Statute, legalEffectAfterReferendum, did not enter into force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalEffectAfterReferendum Context triple: [Saar Statute, legalEffectAfterReferendum, did not enter into force]
-
A.
resultEffectOnBrexit
Indicates the effect or impact that a particular result has on Brexit.
-
B.
legalStatusOfReferendums
chosen
Indicates the legal status or validity assigned to specific referendums within a given legal or constitutional framework.
-
C.
independenceReferendum
Indicates a formal vote in which a population decides whether a territory or region should become politically independent from its current governing state or authority.
-
D.
effectIfRatified
Indicates that a particular effect or outcome will occur if and when an agreement, decision, or measure is formally ratified.
-
E.
referendumResult
Indicates the outcome or decision reached by voters in a specific referendum.
- 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_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 27, 2026, 8:50 p.m.