Triple
T33229926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eustace Scrubb |
E850665
|
entity |
| Predicate | roleInTheSilverChair |
P140406
|
FINISHED |
| Object | co-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: co-protagonist | Statement: [Eustace Scrubb, roleInTheSilverChair, co-protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTheSilverChair Context triple: [Eustace Scrubb, roleInTheSilverChair, co-protagonist]
-
A.
roleInTheWay
Indicates that one entity is obstructing, hindering, or otherwise blocking another entity’s progress, action, or intended path.
-
B.
roleOfCharacter
chosen
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
C.
roleAtLuckyChap
Indicates that an entity holds or held a specific role or position at the organization LuckyChap.
-
D.
roleInTheMangler
Indicates that an entity has a specific role or involvement in the work titled "The Mangler."
-
E.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0076c0a5c4819088b17b95511b93ed |
completed | May 10, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_6a007638a67c81909c091335142260ab |
completed | May 10, 2026, 12:12 p.m. |
Created at: May 1, 2026, 1:30 a.m.