Triple
T31744361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-bomber force |
E810228
|
entity |
| Predicate | laterDoctrine |
P151315
|
FINISHED |
| Object | low-level penetration |
—
|
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: low-level penetration | Statement: [V-bomber force, laterDoctrine, low-level penetration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDoctrine Context triple: [V-bomber force, laterDoctrine, low-level penetration]
-
A.
alternativeDoctrine
Indicates that one doctrine serves as an alternative or substitute to another doctrine within a given context.
-
B.
developedDoctrine
Indicates that one entity created, formulated, or significantly advanced a particular doctrine or set of principles.
-
C.
currentDoctrine
chosen
Indicates the doctrine, policy, or set of guiding principles that is presently in force or officially adopted at a given time.
-
D.
confirmedDoctrine
Indicates that an authority has officially validated, endorsed, or ratified a particular doctrine as true or acceptable.
-
E.
retainedDoctrine
Indicates that a particular doctrine, belief, or principle has been kept in force or maintained over time rather than discarded or replaced.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: April 30, 2026, 11:26 p.m.