Triple
T15318921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staff Platoon Commander Course |
E366235
|
entity |
| Predicate | targetAudienceRank |
P118092
|
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: [Staff Platoon Commander Course, targetAudienceRank, captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAudienceRank Context triple: [Staff Platoon Commander Course, targetAudienceRank, captain]
-
A.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
B.
rankingImpact
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
-
C.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
D.
goRank
Indicates a ranking or ordered position assigned to an entity within a sequence or hierarchy.
-
E.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd356b881908f054b64eee6a371 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:16 a.m.