Triple
T28077890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saar Statute |
E709594
|
entity |
| Predicate | rejectedOn |
P24851
|
FINISHED |
| Object | 23 October 1955 |
—
|
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: 23 October 1955 | Statement: [Saar Statute, rejectedOn, 23 October 1955]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectedOn Context triple: [Saar Statute, rejectedOn, 23 October 1955]
-
A.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
B.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
C.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
D.
rejectedAt
chosen
Indicates the time or date at which something (such as a request, application, or proposal) was formally rejected.
-
E.
rejectedAward
Indicates that an entity refused to accept or declined an award that was offered or granted to it.
- 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_69f64041bf5481909c78a174cd491482 |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:50 p.m.