Triple
T31076339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Anzac (fictional cruiser) |
E791974
|
entity |
| Predicate | characterRankOnBoard |
P103031
|
FINISHED |
| Object | Lieutenant-Commander Peter Holmes |
—
|
NE NERFINISHED |
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: Lieutenant-Commander Peter Holmes | Statement: [HMAS Anzac (fictional cruiser), characterRankOnBoard, Lieutenant-Commander Peter Holmes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterRankOnBoard Context triple: [HMAS Anzac (fictional cruiser), characterRankOnBoard, Lieutenant-Commander Peter Holmes]
-
A.
roleInRanking
Indicates that an entity holds a specific position or function within a particular ranking or ordered list.
-
B.
playedRank
Indicates that an entity participated in an activity, event, or game at a specified rank or position in the ordering.
-
C.
rankInformation
Indicates that information is being ordered or prioritized according to some ranking criteria or relevance.
-
D.
squareRank
Indicates that one entity has a square (second-power) relationship to the rank or position value of another entity.
-
E.
rankingPositions
chosen
Indicates the ordered placement or level assigned to entities within a ranking or 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 29, 2026, 9:02 p.m.