Triple
T19388288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purmerend |
E484991
|
entity |
| Predicate | tradingSpecialization |
P43327
|
FINISHED |
| Object | cattle trade |
—
|
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: cattle trade | Statement: [Purmerend, tradingSpecialization, cattle trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingSpecialization Context triple: [Purmerend, tradingSpecialization, cattle trade]
-
A.
marketSpecialization
chosen
Indicates a relationship where an entity focuses its activities, products, or services on serving a specific segment or niche of a broader market.
-
B.
typeOfTrading
Indicates a relationship where one entity specifies the kind or category of trading activity associated with another entity.
-
C.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
D.
tradingApproach
Indicates the method or strategy an entity uses to conduct trading activities or make trade-related decisions.
-
E.
issuerSpecialization
Indicates the particular field, domain, or area of expertise in which the issuer is specialized.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b425e848190ab5ae8ae0a034fe2 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.