Triple
T16343050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rambouillet Agreement |
E396855
|
entity |
| Predicate | dateOfTalksEnd |
P140
|
FINISHED |
| Object | March 1999 |
—
|
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: March 1999 | Statement: [Rambouillet Agreement, dateOfTalksEnd, March 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfTalksEnd Context triple: [Rambouillet Agreement, dateOfTalksEnd, March 1999]
-
A.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
B.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
endDateOfEntries
Indicates the date on which the referenced entries conclude or are no longer valid.
-
D.
tookPlaceUntil
Indicates that an event or situation occurred continuously or repeatedly up to a specified end time or date, after which it no longer took place.
-
E.
conventionEndTime
Indicates the time at which a convention or formal gathering concludes.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0b88d081908a99cafa8e0ae5db |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.