Triple
T30269883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shannons of Broadway |
E769760
|
entity |
| Predicate | hasTitleCharacterFamily |
P185315
|
FINISHED |
| Object | the Shannons |
—
|
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 Shannons | Statement: [The Shannons of Broadway, hasTitleCharacterFamily, the Shannons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCharacterFamily Context triple: [The Shannons of Broadway, hasTitleCharacterFamily, the Shannons]
-
A.
hasTitleInFamily
Indicates that one entity holds a specific familial title or role in relation to another entity within a family context.
-
B.
hasTitleCharacterFrom
Indicates that a work has a title that includes or is derived from a specific character.
-
C.
hasTitleLetter
Indicates that an entity possesses a specific letter or character within its title.
-
D.
hasTitleCharacterRelation
Indicates a relationship where a title (such as a work or publication) is associated with or linked to a specific character appearing in it.
-
E.
hasTitleCharacterAlias
Indicates that a title (such as a work or publication) is associated with an alternate or alias name for one of its characters.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: April 29, 2026, 7:43 p.m.