Triple
T26523741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centro Sul subregion |
E670628
|
entity |
| Predicate | notableMunicipalityIncluded |
P41762
|
FINISHED |
| Object | Almada |
—
|
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: Almada | Statement: [Centro Sul subregion, notableMunicipalityIncluded, Almada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMunicipalityIncluded Context triple: [Centro Sul subregion, notableMunicipalityIncluded, Almada]
-
A.
notableCityIncluded
chosen
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
B.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
C.
notableHumanSettlement
Indicates that a location is recognized as a significant or noteworthy human settlement, such as a city, town, or village.
-
D.
oftenIncludesMunicipality
Indicates that one entity frequently or typically contains or encompasses a municipality within its boundaries or scope.
-
E.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: April 27, 2026, 1:30 a.m.