Triple
T13978241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgrade Declaration |
E336239
|
entity |
| Predicate | articulatesPrinciple |
P11867
|
FINISHED |
| Object | neutrality |
—
|
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: neutrality | Statement: [Belgrade Declaration, articulatesPrinciple, neutrality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: articulatesPrinciple Context triple: [Belgrade Declaration, articulatesPrinciple, neutrality]
-
A.
establishesPrinciple
chosen
Indicates that an entity formulates, defines, or sets forth a foundational rule, guideline, or standard that others are expected to follow or build upon.
-
B.
principle1
Indicates that one entity serves as a primary rule, guideline, or foundational principle governing or guiding another entity.
-
C.
implementsPrinciple
Indicates that an entity applies, follows, or puts into practice a specified principle in its design, behavior, or operation.
-
D.
recognizesPrinciple
Indicates that an entity acknowledges the validity, authority, or applicability of a particular principle.
-
E.
principle11
Indicates that an entity is governed or characterized by the eleventh principle within a defined ordered set of principles.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e9fc7248190a9f26e253286ac3c |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.