Triple
T11439974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VC DSO MC |
E271116
|
entity |
| Predicate | hasComponentRank |
P84741
|
FINISHED |
| Object | highest gallantry award |
—
|
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: highest gallantry award | Statement: [VC DSO MC, hasComponentRank, highest gallantry award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentRank Context triple: [VC DSO MC, hasComponentRank, highest gallantry award]
-
A.
containsRank
chosen
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
B.
hasRankContext
Indicates that an entity’s rank or ordering is defined, interpreted, or constrained within a specific contextual framework or situation.
-
C.
hasRankVariant
Indicates that one entity is an alternative or variant form of another entity’s rank or hierarchical level.
-
D.
hasComponentCount
Indicates that an entity is associated with a specific number of components it contains or comprises.
-
E.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d80888190c8190b6365550ffe4931c |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.