Triple
T9952753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leon Vance |
E195368
|
entity |
| Predicate | previousRank |
P29271
|
FINISHED |
| Object | Assistant Director of NCIS |
—
|
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: Assistant Director of NCIS | Statement: [Leon Vance, previousRank, Assistant Director of NCIS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousRank Context triple: [Leon Vance, previousRank, Assistant Director of NCIS]
-
A.
formerRanking
chosen
Indicates that an entity previously held a particular rank or position but no longer does so.
-
B.
nextHigherRank
Indicates that one entity holds the immediately superior rank or level in a hierarchy relative to another entity.
-
C.
promotedToRankBy
Indicates that an entity was elevated to a particular rank or position through the action or decision of another entity.
-
D.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb693918081908e9f96ef302235ad |
completed | April 2, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.