Triple
T37184036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagor-nuin-Giliath |
E921273
|
entity |
| Predicate | enemyStrongholdInvolved |
P46785
|
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: [Dagor-nuin-Giliath, enemyStrongholdInvolved, Angband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyStrongholdInvolved Context triple: [Dagor-nuin-Giliath, enemyStrongholdInvolved, Angband]
-
A.
strongholdOf
chosen
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular entity.
-
B.
primaryStronghold
Indicates that one location serves as the main base, fortress, or central stronghold for an entity compared to its other sites.
-
C.
strongholdRegion
Indicates that a stronghold (fortified place or base) is located within or associated with a particular geographic region.
-
D.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
E.
currentStronghold
Indicates that an entity currently serves as the primary base, fortress, or central stronghold for another 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_69f76ea250bc819083f28d81de25cd0c |
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.