Triple
T16084495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNT Express |
E390192
|
entity |
| Predicate | hasRegionalStrength |
P32293
|
FINISHED |
| Object | European road network |
—
|
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: European road network | Statement: [TNT Express, hasRegionalStrength, European road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalStrength Context triple: [TNT Express, hasRegionalStrength, European road network]
-
A.
hasRegionStrongPresence
chosen
Indicates that an entity maintains a significant, influential, or concentrated presence within a specified region.
-
B.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
isRegional
Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
-
E.
hasRegionalRole
Indicates that an entity holds a specific role, function, or responsibility within a defined geographic region.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.