Triple
T37330080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hithlum |
E926719
|
entity |
| Predicate | capitalOrChiefStronghold |
P46785
|
FINISHED |
| Object | Barad Eithel |
—
|
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: Barad Eithel | Statement: [Hithlum, capitalOrChiefStronghold, Barad Eithel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOrChiefStronghold Context triple: [Hithlum, capitalOrChiefStronghold, Barad Eithel]
-
A.
strongholdOf
chosen
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular entity.
-
B.
wasCitadelOf
Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
-
C.
capitalUnder
Indicates that one entity serves as the capital city or administrative center subordinate to, or governed by, another entity.
-
D.
capitalOfLeadingSide
Indicates that one entity is the capital city or primary administrative center of the leading or principal side in a conflict, negotiation, or competitive relationship.
-
E.
capitalCityBuildingOf
Indicates that a building is located in and associated with the capital city of a given political or administrative entity.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 3, 2026, 4:16 p.m.