Triple
T38434820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Squadron |
E903910
|
entity |
| Predicate | typicalSecondInCommandRank |
P175022
|
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: [A Squadron, typicalSecondInCommandRank, captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSecondInCommandRank Context triple: [A Squadron, typicalSecondInCommandRank, captain]
-
A.
rankOfSecondCommander
chosen
Indicates the rank held by the person serving as the second-in-command in a hierarchy or organization.
-
B.
typicalCommandRank
Indicates the usual or most common rank at which an individual typically holds command authority in a given context.
-
C.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
D.
secondRank
Indicates that one entity holds the second position or rank in order or hierarchy relative to others.
-
E.
UnionCommanderSubordinate
Indicates that one person holds a commanding position over another within the same union or allied group, establishing a superior–subordinate relationship in that organizational 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.