Triple
T37107367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cammareri Brothers Bakery |
E918880
|
entity |
| Predicate | hasFictionalOwnerFamilyName |
P84333
|
FINISHED |
| Object | Cammareri |
—
|
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: Cammareri | Statement: [Cammareri Brothers Bakery, hasFictionalOwnerFamilyName, Cammareri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalOwnerFamilyName Context triple: [Cammareri Brothers Bakery, hasFictionalOwnerFamilyName, Cammareri]
-
A.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
B.
ownedByFictionalFamily
Indicates that something is possessed or held in ownership by a fictional family within a narrative or fictional universe.
-
C.
hasFictionalFamilyMember
Indicates that one entity has another entity as a family member within a fictional or imagined context.
-
D.
hasFictionalProprietor
Indicates that something is owned, managed, or run by a fictional character or entity within a narrative context.
-
E.
hasFamilyNameInFiction
chosen
Indicates that a fictional character is associated with a particular family name within a work of fiction.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4:14 p.m.