Triple
T36557457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elves of Lindon |
E901733
|
entity |
| Predicate | maintainedHavens |
P27533
|
FINISHED |
| Object | Grey Havens |
—
|
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: Grey Havens | Statement: [Elves of Lindon, maintainedHavens, Grey Havens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedHavens Context triple: [Elves of Lindon, maintainedHavens, Grey Havens]
-
A.
establishedHaven
Indicates that an entity created or set up a place of safety, refuge, or secure base for others.
-
B.
hadSanctuaryOf
Indicates that an entity possessed or hosted a sanctuary dedicated to another entity.
-
C.
governedSanctuary
Indicates that an entity holds governing authority or administrative control over a sanctuary.
-
D.
maintainedFor
chosen
Indicates that something is kept in a particular state, condition, or operation for the benefit, use, or purpose of another entity.
-
E.
servedHarbour
Indicates that an entity provided service, support, or functions related to a harbour or port.
- 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_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:11 p.m.