Triple
T29020353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duff Lite |
E737434
|
entity |
| Predicate | hasFictionalBrandFamilyMember |
P190479
|
FINISHED |
| Object | Duff Beer |
—
|
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: Duff Beer | Statement: [Duff Lite, hasFictionalBrandFamilyMember, Duff Beer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalBrandFamilyMember Context triple: [Duff Lite, hasFictionalBrandFamilyMember, Duff Beer]
-
A.
hasFictionalFamilyMember
chosen
Indicates that one entity has another entity as a family member within a fictional or imagined context.
-
B.
hasFictionalMember
Indicates that a group, organization, or collection includes at least one member that is fictional rather than real.
-
C.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
D.
ownedByFictionalFamily
Indicates that something is possessed or held in ownership by a fictional family within a narrative or fictional universe.
-
E.
hasFictionalSibling
Indicates that one entity is a fictional character who is a sibling 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 28, 2026, 9:48 a.m.