Triple
T33112409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arveleg I |
E847364
|
entity |
| Predicate | enemyRealm |
P59800
|
FINISHED |
| Object | Angmar |
—
|
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: Angmar | Statement: [Arveleg I, enemyRealm, Angmar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyRealm Context triple: [Arveleg I, enemyRealm, Angmar]
-
A.
realm
Indicates that one entity is a domain, sphere of influence, or area of control associated with another entity.
-
B.
primaryAntagonisticRealmIn
Indicates that an entity’s main or most significant antagonistic or opposing activity occurs within a specified realm or domain.
-
C.
enemyNation
chosen
Indicates that one nation is considered a hostile or adversarial state in relation to another nation.
-
D.
enemyTribe
Indicates that one tribe is in an adversarial or hostile relationship with another tribe.
-
E.
realmConqueredBy
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:27 a.m.