Triple
T17109416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Women’s Royal Naval Service |
E415184
|
entity |
| Predicate | notableRankTitle |
P20021
|
FINISHED |
| Object | Director of the WRNS |
—
|
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: Director of the WRNS | Statement: [Women’s Royal Naval Service, notableRankTitle, Director of the WRNS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRankTitle Context triple: [Women’s Royal Naval Service, notableRankTitle, Director of the WRNS]
-
A.
notableRank
Indicates that an entity holds a distinguished or significant position or level within a ranking or hierarchy.
-
B.
notableOfficerTitle
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
-
C.
notableTitleHeld
chosen
Indicates that an entity has held a distinguished or noteworthy title, rank, or official position.
-
D.
hasRankOrTitle
Indicates that an entity holds, is assigned, or is associated with a specific rank, title, or formal designation.
-
E.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc29c884819092a97d9663a1b1f7 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.