Triple
T17863387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippa Georgiou |
E446128
|
entity |
| Predicate | rankHistory |
P129060
|
FINISHED |
| Object | Captain of the USS Shenzhou |
—
|
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 of the USS Shenzhou | Statement: [Philippa Georgiou, rankHistory, Captain of the USS Shenzhou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankHistory Context triple: [Philippa Georgiou, rankHistory, Captain of the USS Shenzhou]
-
A.
chronRank
Indicates the relative chronological order or ranking of events or time-related entities with respect to one another.
-
B.
nationalRankingHistorical
Indicates the historical position or level an entity held within a national ranking over time.
-
C.
rankingMember
Indicates that one entity is the highest-ranking or most senior member within a particular group, committee, or organization relative to the others.
-
D.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
E.
rankingPositions
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49791b0c08190b04a426bd274065d |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:17 a.m.