Triple
T4394884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euroregion Baltic |
E99462
|
entity |
| Predicate | sectorInvolved |
P2193
|
FINISHED |
| Object | transport and infrastructure |
—
|
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: transport and infrastructure | Statement: [Euroregion Baltic, sectorInvolved, transport and infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorInvolved Context triple: [Euroregion Baltic, sectorInvolved, transport and infrastructure]
-
A.
sectorBenefited
Indicates that a particular sector gains advantage, support, or positive impact from a given action, policy, resource, or entity.
-
B.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
C.
sector
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
D.
sectorRepresented
Indicates that an entity serves as a representative or proxy for a particular sector (such as an industry, domain, or market segment).
-
E.
sectorServed
chosen
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352a9c8b88190a7894a40be4996f0 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:20 p.m.