Triple
T16860517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Air Force Cadets |
E409896
|
entity |
| Predicate | emphasisesValues |
P106668
|
FINISHED |
| Object | discipline |
—
|
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: discipline | Statement: [Australian Air Force Cadets, emphasisesValues, discipline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasisesValues Context triple: [Australian Air Force Cadets, emphasisesValues, discipline]
-
A.
normativelyEmphasizes
chosen
Indicates that one entity highlights, prioritizes, or stresses another entity as a standard, value, or principle that ought to be followed or given special importance.
-
B.
hasEmphasis
Indicates that one element is given special stress, importance, or prominence relative to others.
-
C.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
D.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
E.
emphasizesConsonanceOf
Indicates that one entity highlights, stresses, or draws attention to the harmony, agreement, or consonant relationship between itself and another entity.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b502bc048190baa5a83015407080 |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.