Triple
T34404390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headquarters and Headquarters Company |
E883068
|
entity |
| Predicate | hasRankForCommander |
P30999
|
FINISHED |
| Object | captain |
—
|
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: captain | Statement: [Headquarters and Headquarters Company, hasRankForCommander, captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankForCommander Context triple: [Headquarters and Headquarters Company, hasRankForCommander, captain]
-
A.
hasRankForCommandant
Indicates that an entity holds the specific rank required to serve as a commandant.
-
B.
hasCommanderRank
chosen
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
C.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
D.
hasWingCommanderRank
Indicates that one entity holds the military rank of Wing Commander in relation to another entity or organizational context.
-
E.
hasSaxonCommanderRank
Indicates that an entity holds a military commander rank within a Saxon context or hierarchy.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 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 1, 2026, 1:59 a.m.