Triple
T28974577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhûn |
E734372
|
entity |
| Predicate | conflictsInvolving |
P22787
|
FINISHED |
| Object | wars between Gondor and Easterlings |
—
|
LITERAL FINISHED |
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: wars between Gondor and Easterlings | Statement: [Rhûn, conflictsInvolving, wars between Gondor and Easterlings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictsInvolving Context triple: [Rhûn, conflictsInvolving, wars between Gondor and Easterlings]
-
A.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
B.
notableConflictWith
chosen
Indicates a significant, recognized conflict or dispute that exists or has existed between the related entities.
-
C.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
D.
allyInConflict
Indicates that one entity supports and cooperates with another entity as an ally within the context of a specific conflict or dispute.
-
E.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 9:07 a.m.