Triple
T25210927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archibald Bunker |
E631681
|
entity |
| Predicate | inUniverseHobby |
P158422
|
FINISHED |
| Object | drinking beer |
—
|
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: drinking beer | Statement: [Archibald Bunker, inUniverseHobby, drinking beer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseHobby Context triple: [Archibald Bunker, inUniverseHobby, drinking beer]
-
A.
inUniverseHobby
chosen
Indicates that an entity has a particular hobby or pastime within the context of a specific fictional or defined universe.
-
B.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
C.
isPopularWithHobbyKeepers
Indicates that something is widely liked, favored, or well-regarded by people who pursue a particular hobby or collection activity.
-
D.
formerHobby
Indicates that an activity was previously pursued as a hobby by an entity but is no longer currently practiced as such.
-
E.
favoriteHobby
Indicates that one entity has another entity as the hobby they enjoy doing the most.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 12:58 p.m.