Triple
T36611482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Druedain |
E903476
|
entity |
| Predicate | historicHomeland |
P203243
|
FINISHED |
| Object | Brethil |
—
|
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: Brethil | Statement: [Druedain, historicHomeland, Brethil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicHomeland Context triple: [Druedain, historicHomeland, Brethil]
-
A.
historicCore
Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
-
B.
ethnicHistory
Indicates a relationship where one entity documents, describes, or is associated with the historical development, experiences, or heritage of an ethnic group.
-
C.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
D.
sharesHistoricalLegacyOf
Indicates that one entity is connected to, or participates in, the same historical legacy, tradition, or heritage as another entity.
-
E.
historicalHabitat
Indicates that an entity previously lived, occurred, or was distributed within a particular habitat or environment in the past.
- F. None of above. chosen
Provenance (4 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a01416f8a8c8190abc12f68bd23dcc3 |
completed | May 11, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_6a013f3bc2e48190a51ec2707bbdd474 |
completed | May 11, 2026, 2:30 a.m. |
| PDg | Predicate description generation | batch_6a01416eb9588190ad74541d0640a4ba |
completed | May 11, 2026, 2:39 a.m. |
Created at: May 3, 2026, 4:11 p.m.