Triple
T26671376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Montenegro |
E672338
|
entity |
| Predicate | hasServiceToRegion |
P13639
|
FINISHED |
| Object | Western Europe |
—
|
NE NERFINISHED |
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: Western Europe | Statement: [Air Montenegro, hasServiceToRegion, Western Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceToRegion Context triple: [Air Montenegro, hasServiceToRegion, Western Europe]
-
A.
hasRegionalServices
Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
-
B.
isInhabitedRegionServed
Indicates that a particular inhabited region is provided with services or coverage by a specified entity (such as an organization, facility, or infrastructure).
-
C.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
D.
hasServiceAreas
chosen
Indicates that an entity provides services within, or is operational across, specific geographic or functional areas.
-
E.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 27, 2026, 3:13 a.m.