Triple
T36954551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaver |
E914154
|
entity |
| Predicate | roleInFableIII |
P203692
|
FINISHED |
| Object | industrial magnate of Bowerstone |
—
|
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: industrial magnate of Bowerstone | Statement: [Reaver, roleInFableIII, industrial magnate of Bowerstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFableIII Context triple: [Reaver, roleInFableIII, industrial magnate of Bowerstone]
-
A.
roleInFableII
Indicates that an entity has a specific role or function within the context of the work "Fable II."
-
B.
roleInDiablo
Indicates the specific function, position, or character type an entity has within the context of the Diablo game series.
-
C.
roleInFateZero
Indicates that an entity has a specific narrative or functional role within the context of the Fate/Zero series.
-
D.
roleInShadowlands
Indicates that one entity has a specific function, position, or significance within the context of the Shadowlands.
-
E.
fantasyRole
Indicates that one entity holds a fictional, imaginative, or role-playing identity or function in relation to another within a fantasy or make-believe context.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01c74a72fc819084826c6c292af03a |
completed | May 11, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a01c624103c819087cb35a71c5868b6 |
completed | May 11, 2026, 12:05 p.m. |
| PDg | Predicate description generation | batch_6a01c749c7148190ad49ede859c60b75 |
completed | May 11, 2026, 12:10 p.m. |
Created at: May 3, 2026, 4:13 p.m.