Triple
T12924848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O-1 |
E309216
|
entity |
| Predicate | typicalRankTitle |
P85416
|
FINISHED |
| Object | Ensign |
—
|
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: Ensign | Statement: [O-1, typicalRankTitle, Ensign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRankTitle Context triple: [O-1, typicalRankTitle, Ensign]
-
A.
titleOrRole
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
B.
hasRankOrTitle
Indicates that an entity holds, is assigned, or is associated with a specific rank, title, or formal designation.
-
C.
typicalOfficeHolderTitle
chosen
Indicates the standard or commonly used title typically held by the office holder of a given position or role.
-
D.
lowerOrEqualRankTitle
Indicates that one entity’s rank or title is lower than or equal to the rank or title of another entity.
-
E.
notableOfficerTitle
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e9576c81908eb59569af6da877 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fab4d0881909a7a4d66bab9aa85 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.