Triple
T23877518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hob. XXI:2 |
E592908
|
entity |
| Predicate | principalCharacters |
P39597
|
FINISHED |
| Object | Gabriel |
—
|
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: Gabriel | Statement: [Hob. XXI:2, principalCharacters, Gabriel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalCharacters Context triple: [Hob. XXI:2, principalCharacters, Gabriel]
-
A.
characters
Indicates that one entity is a character (or set of characters) associated with, appearing in, or belonging to another entity (such as a work, story, or medium).
-
B.
mainCharactersAre
chosen
Indicates that the specified entities serve as the primary or central characters in a narrative or work.
-
C.
plotCharacter
Indicates a relationship where a character plays a role or participates in the narrative plot of a story or work.
-
D.
associatedCharacters
Indicates that two or more characters are linked or connected through some relationship, involvement, or relevance to each other.
-
E.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cc02277c8190b0c15d6525f3b38d |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:15 p.m.