Triple
T32113434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandybuck family of Buckland |
E820175
|
entity |
| Predicate | firstKnownMaster |
P206190
|
FINISHED |
| Object | Gorhendad Oldbuck |
E1993295
|
NE 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: Gorhendad Oldbuck | Statement: [Brandybuck family of Buckland, firstKnownMaster, Gorhendad Oldbuck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstKnownMaster Context triple: [Brandybuck family of Buckland, firstKnownMaster, Gorhendad Oldbuck]
-
A.
formerMaster
Indicates that one entity previously held the role of master over another entity, but no longer does so.
-
B.
finalMaster
Indicates that one entity is the ultimate or definitive master, controller, or authoritative source over another entity or process.
-
C.
firstKnownCount
Indicates the earliest recorded quantity or number of instances known for something within a given context.
-
D.
firstKnownLord
Indicates that the subject is the earliest historically or canonically recorded lord associated with the object.
-
E.
firstEncounteredBy
Indicates that one entity is the person or agent who initially discovered, met, or came across the other entity for the first time.
- F. None of above. chosen
Provenance (5 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f3b76e2708190a5d76a40bc983b9d |
completed | June 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:27 a.m.