Triple
T11324495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic fur trade |
E268173
|
entity |
| Predicate | drivingDemandFrom |
P82228
|
FINISHED |
| Object | European fashion markets |
—
|
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: European fashion markets | Statement: [Atlantic fur trade, drivingDemandFrom, European fashion markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingDemandFrom Context triple: [Atlantic fur trade, drivingDemandFrom, European fashion markets]
-
A.
drives
Indicates that one entity operates and controls the movement of a vehicle or similar conveyance transporting themselves or others.
-
B.
promptedDemandFor
chosen
Indicates that one entity’s action or occurrence caused an increase in demand for another entity.
-
C.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
D.
demand
Indicates that one entity requests or insists that another entity provide something or perform an action, often with an expectation of compliance.
-
E.
demands
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e122e48190b3f890de8d561480 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.