Triple
T37961308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boy Blue |
E947013
|
entity |
| Predicate | roleInFabletown |
P203988
|
FINISHED |
| Object | clerk |
—
|
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: clerk | Statement: [Boy Blue, roleInFabletown, clerk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFabletown Context triple: [Boy Blue, roleInFabletown, clerk]
-
A.
roleInFables
chosen
Indicates that an entity serves a particular narrative or functional role within one or more fables.
-
B.
roleInFableIII
Indicates that an entity has a specific role or function within the context of the work "Fable III."
-
C.
roleInFableII
Indicates that an entity has a specific role or function within the context of the work "Fable II."
-
D.
roleInRiseOfShadows
Indicates the specific part or function an entity plays within the context of the "Rise of Shadows" event or storyline.
-
E.
roleInOldTown
Indicates that an entity holds or held a specific role, position, or function within the context of Old Town.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a031045669c8190944781a48d09b5b6 |
completed | May 12, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_6a030fa775848190839b388f950d0364 |
completed | May 12, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:20 p.m.