Triple
T24795289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bordoy |
E620362
|
entity |
| Predicate | hasRegionCapitalFunction |
P145877
|
FINISHED |
| Object | Norðoyar region |
—
|
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: Norðoyar region | Statement: [Bordoy, hasRegionCapitalFunction, Norðoyar region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionCapitalFunction Context triple: [Bordoy, hasRegionCapitalFunction, Norðoyar region]
-
A.
hasCapitalRegionRelation
Indicates a relationship where one entity serves as the capital region or administrative capital area of another entity.
-
B.
capitalOfRegionContext
chosen
Indicates that a location serves as the capital city or administrative center within the context of a specific region.
-
C.
countryCapitalRegionFor
Indicates that a specified region serves as the capital area or administrative capital region for a given country.
-
D.
countryCapitalRegion
Indicates that a specified region is the capital region (administrative capital area) of a given country.
-
E.
hasNationalCapitalFunction
Indicates that an entity serves as the national capital or performs the official capital-city role for a country or sovereign state.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 4:48 a.m.