Triple
T36557132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Dragon Inn |
E901726
|
entity |
| Predicate | primaryPatrons |
P34539
|
FINISHED |
| Object | hobbits |
—
|
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: hobbits | Statement: [Green Dragon Inn, primaryPatrons, hobbits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPatrons Context triple: [Green Dragon Inn, primaryPatrons, hobbits]
-
A.
primaryPatron
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
B.
primaryMembers
Indicates that the related entities are the main or most important members within a larger group or organization.
-
C.
coPatron
Indicates a relationship where two or more entities share joint responsibility or role as patrons supporting the same person, group, or endeavor.
-
D.
primaryVisitors
chosen
Indicates that certain entities are the main or most important visitors associated with another entity or context.
-
E.
traditionalPatron
Indicates a relationship where one entity serves as a customary or historically established patron or supporter of another.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.