Triple
T33229928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eustace Scrubb |
E850665
|
entity |
| Predicate | roleInTheLastBattle |
P28183
|
FINISHED |
| Object | supporting character |
—
|
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: supporting character | Statement: [Eustace Scrubb, roleInTheLastBattle, supporting character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTheLastBattle Context triple: [Eustace Scrubb, roleInTheLastBattle, supporting character]
-
A.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
B.
roleInWarOrConflict
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
C.
foughtAs
Indicates that an entity participated in a conflict or war in the capacity, role, or identity specified by another entity.
-
D.
battleParticipated
Indicates that an entity took part in a specific battle as a combatant or participant.
-
E.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
- 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_6a00781b749c8190921c46e110cae0b0 |
completed | May 10, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_6a0077df3c8481909fabc9e84f5936e3 |
completed | May 10, 2026, 12:19 p.m. |
Created at: May 1, 2026, 1:30 a.m.