Triple
T32206792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Elrond |
E822692
|
entity |
| Predicate | memberChosen |
P24118
|
FINISHED |
| Object | Frodo Baggins |
—
|
NE NERFINISHED |
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: Frodo Baggins | Statement: [Council of Elrond, memberChosen, Frodo Baggins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberChosen Context triple: [Council of Elrond, memberChosen, Frodo Baggins]
-
A.
membershipDecidedBy
Indicates that the determination of whether an entity is granted membership in a group, organization, or set is made by another specified entity or process.
-
B.
memberBecame
chosen
Indicates that an entity transitioned into becoming a member of a group, organization, or collection at a specific point in time.
-
C.
memberReceived
Indicates that a member has obtained or been given something (such as an item, message, or benefit) from another source.
-
D.
memberFrom
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
-
E.
nameChosenToBe
Indicates that an entity has been given or selected to have a particular name.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 12:36 a.m.