Triple
T1144152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEL 20 |
E23524
|
entity |
| Predicate | marketCoverage |
P12320
|
FINISHED |
| Object | Belgian large-cap equities |
—
|
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: Belgian large-cap equities | Statement: [BEL 20, marketCoverage, Belgian large-cap equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketCoverage Context triple: [BEL 20, marketCoverage, Belgian large-cap equities]
-
A.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
B.
marketRegion
chosen
Indicates the geographic or demographic area in which a product, service, or entity is actively marketed or targeted.
-
C.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
-
D.
networkCoverage
Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
-
E.
mediaMarket
Indicates a relationship where a media outlet or content provider serves, targets, or operates within a particular geographic or demographic market.
- 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_69a4bc5008d8819095c1ffb5db5b4911 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.