Triple
T32869577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Horatio Hornblower R.N. |
E840752
|
entity |
| Predicate | hasTitleCharacterRank |
P90523
|
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: [Captain Horatio Hornblower R.N., hasTitleCharacterRank, Captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCharacterRank Context triple: [Captain Horatio Hornblower R.N., hasTitleCharacterRank, Captain]
-
A.
hasRankOrTitle
chosen
Indicates that an entity holds, is assigned, or is associated with a specific rank, title, or formal designation.
-
B.
hasTitleCharacterTrait
Indicates that a title is associated with a specific character trait of an entity.
-
C.
hasTitleCharacterFrom
Indicates that a work has a title that includes or is derived from a specific character.
-
D.
hasMainTitleCharacter
Indicates that a work’s primary or main title is centered on, derived from, or explicitly names a particular character.
-
E.
hasTitleCharacterAction
Indicates that a work’s title explicitly references or is derived from an action performed by a character within that work.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 1:17 a.m.