Triple
T38396867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eksjö |
E900785
|
entity |
| Predicate | urbanAreaStatusSince |
P30463
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Eksjö, urbanAreaStatusSince, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanAreaStatusSince Context triple: [Eksjö, urbanAreaStatusSince, 15th century]
-
A.
urbanStatusSince
chosen
Indicates the point in time since which an entity has held an urban status or classification.
-
B.
cityStatusUntil
Indicates the period up to a specified time during which a place holds or held a particular city status.
-
C.
hasUrbanDistrictStatusSince
Indicates that an entity has held the legal or administrative status of an urban district continuously since a specified point in time.
-
D.
cityDistrictStatus
Indicates the administrative or legal status that a city district holds within its governing jurisdiction.
-
E.
urbanStatusChange
Indicates a change in an entity’s classification or condition related to its urban status, such as becoming urbanized, de-urbanized, or shifting between different urban categories.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.