Triple
T14691881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billingsgate Market |
E345053
|
entity |
| Predicate | hasNumberOfTradersApproximate |
P115361
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [Billingsgate Market, hasNumberOfTradersApproximate, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfTradersApproximate Context triple: [Billingsgate Market, hasNumberOfTradersApproximate, 100]
-
A.
typicalNumberOfHolders
Indicates the usual or expected number of entities that hold or possess a given item, role, or resource.
-
B.
hasMarketMakers
Indicates that an entity is associated with one or more market makers who provide liquidity or facilitate trading for it.
-
C.
hasTradingDays
Indicates that an entity is associated with specific days on which trading or commercial transactions are conducted.
-
D.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an entity.
-
E.
approximateFolioCount
Indicates an estimated or rough number of folios associated with an entity, rather than an exact counted total.
- F. None of above. chosen
Provenance (4 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb585d46c81908d6964130914cec4 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.