Triple
T2003422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BG Freight Line |
E43521
|
entity |
| Predicate | focusesOnMarket |
P28886
|
FINISHED |
| Object | intra-European trade |
—
|
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: intra-European trade | Statement: [BG Freight Line, focusesOnMarket, intra-European trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnMarket Context triple: [BG Freight Line, focusesOnMarket, intra-European trade]
-
A.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
B.
coreMarket
chosen
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
-
C.
relatedMarket
Indicates that two markets are connected or associated, such that activity, conditions, or changes in one market are relevant to or influence the other.
-
D.
brandFocus
Indicates that a brand primarily concentrates its efforts, messaging, or resources on a particular target, theme, or market segment.
-
E.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8833a54819096301f3ea29ff3a1 |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.