Triple
T27573669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warsaw Pact advisers |
E696099
|
entity |
| Predicate | wereCoordinatedBy |
P155131
|
FINISHED |
| Object | Warsaw Pact Unified Command |
—
|
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: Warsaw Pact Unified Command | Statement: [Warsaw Pact advisers, wereCoordinatedBy, Warsaw Pact Unified Command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereCoordinatedBy Context triple: [Warsaw Pact advisers, wereCoordinatedBy, Warsaw Pact Unified Command]
-
A.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
B.
coordinatedUnder
chosen
Indicates that one entity is organized, directed, or managed under the authority or coordination of another entity.
-
C.
coordinatedFrom
Indicates that an action, event, or process is organized, directed, or managed starting from a particular source location or entity.
-
D.
rescueCoordinatedBy
Indicates that a rescue operation is organized, directed, or managed by a particular coordinating entity.
-
E.
coordina
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group toward a common goal.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:44 p.m.