Triple
T35747925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRBY |
E1033237
|
entity |
| Predicate | tradesInMarketSegment |
P64613
|
FINISHED |
| Object | LSE Main Market |
—
|
NE NERFINISHED |
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: LSE Main Market | Statement: [BRBY, tradesInMarketSegment, LSE Main Market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradesInMarketSegment Context triple: [BRBY, tradesInMarketSegment, LSE Main Market]
-
A.
tradingSegment
chosen
Indicates that one entity operates within, or is associated with, a specific trading segment or market subdivision for transactional activities.
-
B.
tradesInstrument
Indicates that one party engages in buying, selling, or exchanging a specified financial or tradable instrument.
-
C.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
D.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
E.
isTradedBy
Indicates that an item, asset, or resource is exchanged or dealt with by a particular agent, party, or trading entity.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1954f3c81909a38104d1146e162 |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.