Triple
T37142523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fingolfin’s realm in Hithlum |
E920152
|
entity |
| Predicate | frontierAgainst |
P165704
|
FINISHED |
| Object | Angband |
—
|
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: Angband | Statement: [Fingolfin’s realm in Hithlum, frontierAgainst, Angband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontierAgainst Context triple: [Fingolfin’s realm in Hithlum, frontierAgainst, Angband]
-
A.
frontierSystem
Indicates a system that lies at or near the boundary or edge of a defined region, domain, or area of control.
-
B.
frontierWith
chosen
Indicates that two regions or territories share a common boundary or border, especially one marking the edge of settled or controlled area.
-
C.
northernFrontier
Indicates that one entity serves as the northern boundary, edge, or frontier region relative to another entity.
-
D.
frontierDispute
Indicates a conflict or disagreement between entities over the location, control, or status of a shared boundary or border.
-
E.
establishesFrontier
Indicates the action or relationship by which a boundary or frontier is formally created, defined, or set between entities.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.