Triple
T3502872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curse of the Billy Goat |
E74007
|
entity |
| Predicate | originatorOccupation |
P13413
|
FINISHED |
| Object | tavern owner |
—
|
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: tavern owner | Statement: [Curse of the Billy Goat, originatorOccupation, tavern owner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatorOccupation Context triple: [Curse of the Billy Goat, originatorOccupation, tavern owner]
-
A.
creatorOccupation
chosen
Indicates the professional role or job that the creator of an entity holds or held.
-
B.
authorOccupation
Indicates the professional role or job that an author holds or is associated with.
-
C.
visionaryOccupation
Indicates that an entity holds an occupation or role characterized by forward-thinking, innovative, or visionary activities or responsibilities.
-
D.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
E.
recipientOccupation
Indicates that the object specifies the job, profession, or role held by the recipient in the described relationship or 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf0c2b48190b49923137bb9e45d |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.