Triple
T20273914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Produce Exchange |
E502960
|
entity |
| Predicate | hadTradingFloor |
P5156
|
FINISHED |
| Object | grain futures |
—
|
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: grain futures | Statement: [New York Produce Exchange, hadTradingFloor, grain futures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadTradingFloor Context triple: [New York Produce Exchange, hadTradingFloor, grain futures]
-
A.
hasTradingFloor
chosen
Indicates that an entity operates or contains a physical or virtual trading floor where financial instruments are actively bought and sold.
-
B.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
C.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
D.
hadTradingPostNetwork
Indicates that an entity maintained or controlled a network of trading posts used for commercial exchange or trade activities.
-
E.
hasTradingDesk
Indicates that an entity maintains or operates a trading desk function for executing financial trades or market transactions.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675e104f081909d17c1963a5db528 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:31 a.m.