Triple
T4663903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dayman |
E102797
|
entity |
| Predicate | targetAudienceInUniverse |
P10804
|
FINISHED |
| Object | Paddy's Pub patrons |
—
|
LITERAL FINISHED |
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: Paddy's Pub patrons | Statement: [Dayman, targetAudienceInUniverse, Paddy's Pub patrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAudienceInUniverse Context triple: [Dayman, targetAudienceInUniverse, Paddy's Pub patrons]
-
A.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
B.
homeMediumInUniverse
Indicates that a given medium serves as the primary or native environment for something within a particular fictional or conceptual universe.
-
C.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
D.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
E.
associatedUniverse
Indicates that one entity is linked or belongs to a particular universe, realm, or overarching world 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd633aeba88190a8329ed022d685b6 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.