Triple
T29296540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pietas Iulia |
E742845
|
entity |
| Predicate | continuityOfUrbanSettlement |
P177128
|
FINISHED |
| Object | Pula |
—
|
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: Pula | Statement: [Pietas Iulia, continuityOfUrbanSettlement, Pula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuityOfUrbanSettlement Context triple: [Pietas Iulia, continuityOfUrbanSettlement, Pula]
-
A.
hasUrbanContinuity
Indicates that there is a continuous, uninterrupted urbanized area or built-up fabric between the related entities.
-
B.
urbanContinuity
Indicates that two or more urban areas are spatially connected or form a continuous built-up zone without significant gaps.
-
C.
partOfUrbanContinuumWith
Indicates that two or more settlements are spatially and functionally connected in such a way that they form a continuous urban area or built-up zone.
-
D.
permanentHumanSettlement
Indicates that a location serves as a long-term, continuously inhabited place where humans live and establish enduring residence.
-
E.
continuousInhabitation
chosen
Indicates that an entity has lived or been present in a place without interruption over a period of time.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 1:06 p.m.