Triple
T8260701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conventional Armed Forces in Europe Treaty |
E193183
|
entity |
| Predicate | adaptationSignedOn |
P80378
|
FINISHED |
| Object | 1999-11-19 |
—
|
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: 1999-11-19 | Statement: [Conventional Armed Forces in Europe Treaty, adaptationSignedOn, 1999-11-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptationSignedOn Context triple: [Conventional Armed Forces in Europe Treaty, adaptationSignedOn, 1999-11-19]
-
A.
establishedByAgreementSignedIn
Indicates that something was formally created or instituted as a result of an agreement that was signed at a specific time or place.
-
B.
signOnDate
chosen
Indicates the date on which an entity formally signs or enters into an agreement, contract, or system.
-
C.
adaptationStatus
Indicates the current state or progress of how something has been adapted or adjusted in response to specific conditions, requirements, or contexts.
-
D.
signedDuring
Indicates that an agreement, document, or contract was signed within a specified time period or during a particular event.
-
E.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7936b72c8190b998da033df611d1 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.