Triple
T21812702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Dairy Agreement |
E538516
|
entity |
| Predicate | wasRenegotiated |
P145749
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [International Dairy Agreement, wasRenegotiated, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRenegotiated Context triple: [International Dairy Agreement, wasRenegotiated, 1977]
-
A.
periodicallyRenegotiated
Indicates that the terms or conditions of a relationship, agreement, or arrangement are reviewed and adjusted at regular, recurring intervals.
-
B.
negotiatedAfter
Indicates that one negotiation event occurred later in time than another referenced event or negotiation.
-
C.
wasReconfiguredIn
Indicates that an entity underwent a change in its configuration or setup during a specified time or event.
-
D.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
E.
wasReconstructed
Indicates that something previously existing was rebuilt or restored after damage, destruction, or alteration.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc7ec1c8190a5420b44a49ae32f |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c670ee608190b9cfdc09de74f0de |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 6:53 p.m.