Triple
T28077896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saar Statute |
E709594
|
entity |
| Predicate | wouldHaveEstablished |
P164391
|
FINISHED |
| Object | special European statute for Saar |
—
|
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: special European statute for Saar | Statement: [Saar Statute, wouldHaveEstablished, special European statute for Saar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wouldHaveEstablished Context triple: [Saar Statute, wouldHaveEstablished, special European statute for Saar]
-
A.
wouldHaveSucceededFrom
Indicates that a particular outcome or goal would have been successfully achieved starting from a specified prior state or condition, typically under certain hypothetical or counterfactual circumstances.
-
B.
wouldHaveBeenCreatedBy
Indicates that an entity is hypothesized or counterfactually assumed to have been brought into existence by a particular agent or creator under certain conditions.
-
C.
claimedToHaveEstablished
Indicates that an entity asserts or alleges that it has created, founded, or set up another entity, organization, or structure.
-
D.
wouldHaveHeldPosition
Indicates that an entity was expected or intended to occupy a particular role or office, but did not actually hold it in reality.
-
E.
wouldHaveHadMembers
Indicates a hypothetical or counterfactual relationship in which an entity, under certain conditions or in an unrealized scenario, would have included specific members.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 8:50 p.m.