Triple
T36246395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oropher |
E891672
|
entity |
| Predicate | ledForcesIn |
P184802
|
FINISHED |
| Object | Battle of Dagorlad |
—
|
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: Battle of Dagorlad | Statement: [Oropher, ledForcesIn, Battle of Dagorlad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledForcesIn Context triple: [Oropher, ledForcesIn, Battle of Dagorlad]
-
A.
ledForcesFrom
Indicates that one entity commanded or directed military or armed forces originating from another entity or location.
-
B.
inForceIn
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
-
C.
inForceWith
Indicates that a rule, condition, or agreement is currently active and being applied in conjunction with a specified entity or set of entities.
-
D.
typeOfForcesDirected
Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
-
E.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
- 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5f89c5c8190825ed5d4317c540c |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.