Triple
T36544586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Men of Rhûn |
E901106
|
entity |
| Predicate | thirdAgeHistory |
P37550
|
FINISHED |
| Object | repeatedly warred against Gondor |
—
|
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: repeatedly warred against Gondor | Statement: [Men of Rhûn, thirdAgeHistory, repeatedly warred against Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdAgeHistory Context triple: [Men of Rhûn, thirdAgeHistory, repeatedly warred against Gondor]
-
A.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
B.
historicallyGivenTo
Indicates that something was transferred or bestowed upon an entity at some point in the past, typically as recorded or recognized in historical accounts.
-
C.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
-
D.
hasPriorHistory
Indicates that an entity has a previously recorded occurrence, condition, or involvement relevant to the current context.
-
E.
laterLifeEvent
Indicates that one event, condition, or action occurs during a later stage in an entity’s life relative to earlier life phases.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.