Triple
T2976130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palu |
E80399
|
entity |
| Predicate | hasUrbanStatusSince |
P30463
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Palu, hasUrbanStatusSince, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanStatusSince Context triple: [Palu, hasUrbanStatusSince, 20th century]
-
A.
urbanStatusSince
chosen
Indicates the point in time since which an entity has held an urban status or classification.
-
B.
hasUrbanRole
Indicates that an entity plays a specific functional or social role within an urban or city context.
-
C.
hasUrbanFunction
Indicates that an entity serves a specific role or purpose within an urban context, such as providing services, infrastructure, or activities typical of a city environment.
-
D.
hasUrbanClassification
Indicates that an entity is assigned a specific urban status or category within a defined classification system.
-
E.
hasUrbanGminaStatus
Indicates that an administrative unit holds the legal status of an urban gmina (urban municipality).
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad998ad5308190a012ec4940eb46cb |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.