Triple
T11661377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Rawalpindi |
E277126
|
entity |
| Predicate | captainRank |
P31052
|
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: [HMS Rawalpindi, captainRank, Captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captainRank Context triple: [HMS Rawalpindi, captainRank, Captain]
-
A.
navalRankContext
Indicates the relationship between an entity and its naval rank within a specific organizational, temporal, or situational context.
-
B.
captain
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
C.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
D.
captainPosition
chosen
Indicates that an entity holds the role or position of captain in relation to another entity (such as a team, vessel, or group).
-
E.
commanderInChiefRank
Indicates that an entity holds the highest-ranking leadership position over a military or armed forces organization.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d29fdc8190af46b6e2badb1df5 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.