Triple
T12394360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dale |
E296077
|
entity |
| Predicate | prosperedThrough |
P11693
|
FINISHED |
| Object | trade with Erebor |
—
|
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: trade with Erebor | Statement: [Dale, prosperedThrough, trade with Erebor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prosperedThrough Context triple: [Dale, prosperedThrough, trade with Erebor]
-
A.
prosperedFrom
chosen
Indicates that one entity gained benefit, success, or advantage as a result of another entity, event, or circumstance.
-
B.
progressedBy
Indicates that an activity, process, or state advances or moves forward as a result of the actions or influence of a specified agent or factor.
-
C.
historicalPeriodOfProsperity
Indicates a time span in which a society, region, or entity experienced notable economic growth, stability, and overall flourishing.
-
D.
flourishedAlong
Indicates that an entity experienced growth, prosperity, or peak activity in association with a particular period, context, or accompanying entity.
-
E.
becameProfitable
Indicates that an entity transitioned from operating at a loss or break-even to generating a net profit.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd228488190b216abd1c341563c |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.