Triple
T37835540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bigby Wolf |
E943326
|
entity |
| Predicate | roleInFables |
P203988
|
FINISHED |
| Object | sheriff of Fabletown |
—
|
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: sheriff of Fabletown | Statement: [Bigby Wolf, roleInFables, sheriff of Fabletown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFables Context triple: [Bigby Wolf, roleInFables, sheriff of Fabletown]
-
A.
roleInFableIII
Indicates that an entity has a specific role or function within the context of the work "Fable III."
-
B.
roleInFableII
Indicates that an entity has a specific role or function within the context of the work "Fable II."
-
C.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
D.
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.
-
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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a030425fa1c81908748583513552d2b |
completed | May 12, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0303ced28081908588b8a14c23efe9 |
completed | May 12, 2026, 10:41 a.m. |
| PDg | Predicate description generation | batch_6a030424ef5c8190996818517b3e3d51 |
completed | May 12, 2026, 10:42 a.m. |
Created at: May 3, 2026, 4:19 p.m.