Triple
T34501987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verver |
E885780
|
entity |
| Predicate | fictionalFamilyNameIn |
P84333
|
FINISHED |
| Object | The Golden Bowl |
—
|
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: The Golden Bowl | Statement: [Verver, fictionalFamilyNameIn, The Golden Bowl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalFamilyNameIn Context triple: [Verver, fictionalFamilyNameIn, The Golden Bowl]
-
A.
familySurnameInStory
Indicates that a particular family surname appears within the narrative or context of a given story.
-
B.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
-
C.
hasFamilyNameInFiction
chosen
Indicates that a fictional character is associated with a particular family name within a work of fiction.
-
D.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
E.
nameFamily
Indicates that one entity is the family name (surname) of another entity.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: May 1, 2026, 2:01 a.m.