Triple
T1140436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankfurt Stock Exchange |
E23436
|
entity |
| Predicate | hasFloorTrading |
P5156
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Frankfurt Stock Exchange, hasFloorTrading, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloorTrading Context triple: [Frankfurt Stock Exchange, hasFloorTrading, yes]
-
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.
hasTradingHours
Indicates that an entity operates or is available for trading during specified time periods.
-
D.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
E.
hasElectronicTradingSystem
Indicates that an entity operates or utilizes an electronic system for executing trades or 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.