Triple
T37486492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Defence Course |
E931544
|
entity |
| Predicate | participantRank |
P113769
|
FINISHED |
| Object | senior commissioned officers |
—
|
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: senior commissioned officers | Statement: [National Defence Course, participantRank, senior commissioned officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantRank Context triple: [National Defence Course, participantRank, senior commissioned officers]
-
A.
attendanceRank
Indicates the relative position or level of an entity in terms of how frequently or consistently it attends compared to others.
-
B.
partnerRank
Indicates the relative status or level assigned to a partner within a partnership or collaboration hierarchy.
-
C.
roleInRanking
chosen
Indicates that an entity holds a specific position or function within a particular ranking or ordered list.
-
D.
rankingPositions
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
-
E.
rankingMember
Indicates that one entity is the highest-ranking or most senior member within a particular group, committee, or organization relative to the others.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:17 p.m.