Triple
T35677681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enso |
E1030908
|
entity |
| Predicate | subsequentStatusConfirmedBy |
P169385
|
FINISHED |
| Object | Paris Peace Treaty (1947) |
—
|
NE NERFINISHED |
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: Paris Peace Treaty (1947) | Statement: [Enso, subsequentStatusConfirmedBy, Paris Peace Treaty (1947)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentStatusConfirmedBy Context triple: [Enso, subsequentStatusConfirmedBy, Paris Peace Treaty (1947)]
-
A.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
B.
confirmedAs
Indicates that one entity has been officially verified, recognized, or validated as being identical to or serving in the role of another entity.
-
C.
lostStatusConfirmedBy
Indicates that the confirmation or verification of an item’s lost status is provided or asserted by a specific agent or source.
-
D.
confirmedStatusQuo
Indicates that an existing situation, condition, or arrangement has been reviewed and explicitly affirmed to remain unchanged.
-
E.
reconfirmedAfter
chosen
Indicates that something has been confirmed again at a later time following an earlier confirmation.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fe797d8819093cbda1a02d59dc2 |
completed | May 3, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.