Triple
T28481025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJP-01 |
E720688
|
entity |
| Predicate | isPrimaryDoctrineFor |
P61907
|
FINISHED |
| Object | NATO joint operations |
—
|
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: NATO joint operations | Statement: [AJP-01, isPrimaryDoctrineFor, NATO joint operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryDoctrineFor Context triple: [AJP-01, isPrimaryDoctrineFor, NATO joint operations]
-
A.
primaryDoctrine
chosen
Indicates that the object represents the main or foundational doctrine associated with the subject.
-
B.
isRelevantToDoctrine
Indicates that something has a meaningful connection or applicability to a particular doctrine, principle, or set of beliefs.
-
C.
isPrimary
Indicates that one entity holds the main, leading, or most important role or status in relation to another entity or within a given context.
-
D.
isPartOfDoctrineArea
Indicates that one concept, topic, or element belongs to or falls within the scope of a particular doctrinal area or field of doctrine.
-
E.
confirmedDoctrine
Indicates that an authority has officially validated, endorsed, or ratified a particular doctrine as true or acceptable.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 2:55 a.m.