Triple
T7086548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erdut Agreement |
E165088
|
entity |
| Predicate | timeframeOfImplementation |
P302
|
FINISHED |
| Object | 1996–1998 |
—
|
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: 1996–1998 | Statement: [Erdut Agreement, timeframeOfImplementation, 1996–1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeframeOfImplementation Context triple: [Erdut Agreement, timeframeOfImplementation, 1996–1998]
-
A.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
B.
timeFrameSpecified
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
C.
foreseesImplementationPeriodOf
Indicates that one entity anticipates or plans the future time frame during which another entity will be implemented or carried out.
-
D.
timeHorizonOfImpact
Indicates the span of time over which an action, event, or factor is expected to produce its effects or consequences.
-
E.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e512bda88190920ecb54b177e569 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.