Triple
T31068515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silverbridge |
E791748
|
entity |
| Predicate | representedInFictionBy |
P192578
|
FINISHED |
| Object | Gerard Maule |
—
|
NE NERFINISHED |
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: Gerard Maule | Statement: [Silverbridge, representedInFictionBy, Gerard Maule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedInFictionBy Context triple: [Silverbridge, representedInFictionBy, Gerard Maule]
-
A.
appearsInFictionAs
chosen
Indicates that one entity is depicted or represented as a character, figure, or element within a fictional work or narrative.
-
B.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
C.
fictionalCharacterPortrayedFromWorkBy
Indicates that a fictional character is depicted or portrayed in a work that was created by a specific author or creator.
-
D.
livesInFiction
Indicates that one entity exists or resides within the fictional world or narrative setting created by another entity.
-
E.
createsInFiction
Indicates that one entity is the creator or originator of another entity within a fictional or narrative context.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 29, 2026, 9:01 p.m.