Triple
T30600183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Dale |
E778882
|
entity |
| Predicate | hasDefensiveAlliancesWith |
P136406
|
FINISHED |
| Object | Erebor |
—
|
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: Erebor | Statement: [Kingdom of Dale, hasDefensiveAlliancesWith, Erebor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefensiveAlliancesWith Context triple: [Kingdom of Dale, hasDefensiveAlliancesWith, Erebor]
-
A.
involvesAlliance
Indicates that there exists a cooperative or strategic alliance relationship between the referenced entities.
-
B.
hasBrokenAllianceWith
Indicates that a previously established alliance or partnership between two entities has been ended or violated by at least one of them.
-
C.
alliesOf
chosen
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
-
D.
alliesIncluded
Indicates that the specified set or group explicitly includes one or more allied entities as members.
-
E.
vassalOrAllyOf
Indicates that one entity is subordinate to, dependent on, or formally aligned in support of another entity, typically in a hierarchical or cooperative political or military relationship.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 29, 2026, 8:25 p.m.