Triple
T35127046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Doctrine Publication on Agile Combat Support |
E1014335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | doctrinal guide |
C11361
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: doctrinal guide Context triple: [Air Force Doctrine Publication on Agile Combat Support, instanceOf, doctrinal guide]
-
A.
doctrinal publication
chosen
A doctrinal publication is an authoritative document that systematically presents, explains, and standardizes the official principles, beliefs, or operational methods of an institution or field.
-
B.
doctrinal discourse
Doctrinal discourse is a structured, often authoritative form of communication that articulates, interprets, and debates the principles, beliefs, and rules of a particular religious, ideological, or theoretical system.
-
C.
doctrinal system
A doctrinal system is an organized, coherent set of principles, beliefs, or teachings that provides a structured framework for understanding, interpreting, and guiding thought or behavior within a particular domain.
-
D.
theological document
A theological document is a written work that systematically explores, explains, or argues about religious beliefs, doctrines, and practices within a particular faith tradition.
-
E.
section of doctrinal statement
A section of doctrinal statement is a distinct, thematically organized subdivision of a formal belief document that articulates specific theological positions or teachings within the overall doctrinal framework.
- F. None of above.
Provenance (1 batch)
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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.