Triple
T28287457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrusovo |
E713322
|
entity |
| Predicate | coordinateAgreement |
P168965
|
FINISHED |
| Object | Truce of Andrusovo |
—
|
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: Truce of Andrusovo | Statement: [Andrusovo, coordinateAgreement, Truce of Andrusovo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateAgreement Context triple: [Andrusovo, coordinateAgreement, Truce of Andrusovo]
-
A.
coordinateRoleIn
Indicates a relationship where one entity organizes, aligns, or manages the roles or responsibilities of another entity within a shared activity, structure, or context.
-
B.
coordinatesDoctrineIn
Indicates that one entity organizes and aligns doctrinal matters or policies within a specified context, domain, or location.
-
C.
coordinates
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
-
D.
coordinatesUseOf
Indicates that one entity organizes and manages the collaborative use or deployment of another entity’s resources, actions, or functions.
-
E.
mayCoordinate
Indicates that one entity is permitted or has the option to coordinate or work jointly with another entity.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 11:27 p.m.