Triple
T19632219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldenburg, Germany |
E471297
|
entity |
| Predicate | isIndependentCity |
P98838
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oldenburg, Germany, isIndependentCity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIndependentCity Context triple: [Oldenburg, Germany, isIndependentCity, true]
-
A.
hasIndependentCity
Indicates that a larger administrative region or entity contains a city that is administratively independent from the surrounding local jurisdictions.
-
B.
independentCityStatus
chosen
Indicates that a city functions as an administratively independent entity, not subordinated to a surrounding regional or local government unit.
-
C.
isCity
Indicates that the subject entity is classified as a city.
-
D.
isInAutonomousCity
Indicates that one entity is located within a city that has autonomous or self-governing administrative status.
-
E.
isCityOf
Indicates that one entity is a city that belongs to, is located within, or is administratively part of another entity (such as a country, state, or 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641036ee881909fdd8170fe4cdac9 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.