Triple
T23538509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pie Hole |
E577672
|
entity |
| Predicate | hasFictionalMenuItemType |
P114832
|
FINISHED |
| Object | fruit pies |
—
|
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: fruit pies | Statement: [The Pie Hole, hasFictionalMenuItemType, fruit pies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalMenuItemType Context triple: [The Pie Hole, hasFictionalMenuItemType, fruit pies]
-
A.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
B.
hasFictionalProduct
chosen
Indicates a relationship where one entity features, offers, or includes a product that exists only in fiction or an imagined context.
-
C.
hasMenuItem
Indicates that one entity (typically a menu or menu section) includes or offers another entity as one of its menu items.
-
D.
hasFictionalContent
Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
-
E.
hasFictionalEventType
Indicates that something is associated with, characterized by, or classified under a particular type or category of fictional event.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae19473881909aa65f9d36744502 |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.