Triple
T33229927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eustace Scrubb |
E850665
|
entity |
| Predicate | roleInTheVoyageOfTheDawnTreader |
P202372
|
FINISHED |
| Object | major protagonist |
—
|
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: major protagonist | Statement: [Eustace Scrubb, roleInTheVoyageOfTheDawnTreader, major protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTheVoyageOfTheDawnTreader Context triple: [Eustace Scrubb, roleInTheVoyageOfTheDawnTreader, major protagonist]
-
A.
roleInTheGoldenCompass
Indicates that an entity has a specific role or character part in the work "The Golden Compass."
-
B.
roleInTheBlackCauldron
Indicates that an entity has a specific role or appearance in the work "The Black Cauldron."
-
C.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
D.
roleInParadiseLost
Indicates the specific narrative or functional role an entity plays within the work *Paradise Lost*.
-
E.
roleInLegendarium
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00776c4ebc8190899005fda34234d5 |
completed | May 10, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_6a0076f8a4c4819093ed577e67aa38f9 |
completed | May 10, 2026, 12:15 p.m. |
| PDg | Predicate description generation | batch_6a00776b69908190a431a48cc5e7dba9 |
completed | May 10, 2026, 12:17 p.m. |
Created at: May 1, 2026, 1:30 a.m.