Triple
T28553019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Navy captain |
E722937
|
entity |
| Predicate | formalRankTitle |
P301
|
FINISHED |
| Object | Captain, United States Navy |
—
|
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: Captain, United States Navy | Statement: [United States Navy captain, formalRankTitle, Captain, United States Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalRankTitle Context triple: [United States Navy captain, formalRankTitle, Captain, United States Navy]
-
A.
honorificRank
chosen
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
B.
seniorOfficerRank
Indicates that one entity holds a higher or more senior officer rank than the other within a hierarchical structure.
-
C.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
D.
notableOfficerTitle
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
-
E.
commanderTitle
Indicates the official rank or title held by the person who commands or leads a given 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 3:44 a.m.