Triple
T27713399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Oslo, Akershus and Tønsberg |
E698751
|
entity |
| Predicate | associatedWithCapitalRegion |
P12445
|
FINISHED |
| Object | Oslo |
—
|
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: Oslo | Statement: [Duke of Oslo, Akershus and Tønsberg, associatedWithCapitalRegion, Oslo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCapitalRegion Context triple: [Duke of Oslo, Akershus and Tønsberg, associatedWithCapitalRegion, Oslo]
-
A.
hasCapitalRegionRelation
Indicates a relationship where one entity serves as the capital region or administrative capital area of another entity.
-
B.
associatedWithProvinceCapital
Indicates that an entity has a relationship or connection to the capital city of a specific province.
-
C.
regionallyAssociatedWith
chosen
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
D.
connectsToRegionalCapital
Indicates that one location has a direct connection, such as a transport or administrative link, to a designated regional capital.
-
E.
connectsCapitalWithRegion
Indicates a relationship where a capital city is linked or associated with the larger region it belongs to.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a005be4615c8190a710ab704a46c564 |
completed | May 10, 2026, 10:20 a.m. |
| PD | Predicate disambiguation | batch_6a005b8b1cc08190850a392761b84e74 |
completed | May 10, 2026, 10:18 a.m. |
Created at: April 27, 2026, 3:03 p.m.