Triple
T35489979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thorin III Stonehelm |
E1025705
|
entity |
| Predicate | sentForcesTo |
P97478
|
FINISHED |
| Object | Battle of Dale |
—
|
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 Dale | Statement: [Thorin III Stonehelm, sentForcesTo, Battle of Dale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentForcesTo Context triple: [Thorin III Stonehelm, sentForcesTo, Battle of Dale]
-
A.
sendsForcesTo
chosen
Indicates that one entity dispatches or deploys military or security forces to another entity or location.
-
B.
targetedForce
Indicates a deliberate application of force directed at a specific target or entity.
-
C.
associatedForce
Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that entity.
-
D.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
E.
inForceWith
Indicates that a rule, condition, or agreement is currently active and being applied in conjunction with a specified entity or set of entities.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.