Triple
T30600178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Dale |
E778882
|
entity |
| Predicate | sharesEnemiesWith |
P108780
|
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, sharesEnemiesWith, Erebor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesEnemiesWith Context triple: [Kingdom of Dale, sharesEnemiesWith, Erebor]
-
A.
hasCommonEnemies
chosen
Indicates that two or more entities share at least one enemy in common.
-
B.
hasFriendEnemyRelationshipWith
Indicates a relationship where two entities are simultaneously connected as both friends and enemies, reflecting a mixed or ambivalent association between them.
-
C.
sharesGameWithEnemy
Indicates that an entity participates in the same game or match as an opposing or enemy entity.
-
D.
sharesFateWith
Indicates that two or more entities are bound to experience the same outcome, destiny, or consequences.
-
E.
archenemyOf
Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
- 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_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 29, 2026, 8:25 p.m.