Triple
T449501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki Accords |
E7095
|
entity |
| Predicate | signatoryBloc |
P14945
|
FINISHED |
| Object | Western bloc |
—
|
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: Western bloc | Statement: [Helsinki Accords, signatoryBloc, Western bloc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatoryBloc Context triple: [Helsinki Accords, signatoryBloc, Western bloc]
-
A.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
B.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
-
C.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
D.
signatureEvent
Indicates an event in which an entity formally signs or authorizes something, such as a document, agreement, or record.
-
E.
signatoryGovernment
Indicates that a government is a formal signer or ratifying party to an agreement, treaty, or similar binding instrument.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef6755a08190a057e72279b70456 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede1a1108190a4a06b3416ae6156 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef611b9c8190ac5e9174744d9127 |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.