Triple
T29032054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riders of Rohan |
E737752
|
entity |
| Predicate | entersBattle |
P170410
|
FINISHED |
| Object | on horseback |
—
|
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: on horseback | Statement: [Riders of Rohan, entersBattle, on horseback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entersBattle Context triple: [Riders of Rohan, entersBattle, on horseback]
-
A.
AliRecordEnteringFight
Indicates that an entity records or logs the event of another entity entering into a fight or combat situation.
-
B.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
C.
championEnteringBout
Indicates that an entity who holds a championship title is entering or participating in a competitive bout or match.
-
D.
setInBattle
Indicates that an event, scene, or narrative takes place within the context of a battle or active combat situation.
-
E.
combatDebut
Indicates the event or moment when an entity first participates in combat or a fight.
- F. None of above. chosen
Provenance (4 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 28, 2026, 9:56 a.m.