Triple
T33821520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cante Alentejano |
E866839
|
entity |
| Predicate | notableMunicipalCenters |
P102273
|
FINISHED |
| Object | Serpa |
E195642
|
NE 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: Serpa | Statement: [Cante Alentejano, notableMunicipalCenters, Serpa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMunicipalCenters Context triple: [Cante Alentejano, notableMunicipalCenters, Serpa]
-
A.
notablePopulationCenter
Indicates that a location is recognized as a significant or prominent center of population within a given area or context.
-
B.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
C.
notableHumanSettlement
chosen
Indicates that a location is recognized as a significant or noteworthy human settlement, such as a city, town, or village.
-
D.
notableRegionOfSettlement
Indicates that a specified region is a significant or prominent place where an entity is or has been settled.
-
E.
capitalOrMajorCenter
Indicates that a location serves as a capital city or a primary major center (political, economic, or cultural hub) for a larger region or entity.
- F. None of above.
Provenance (4 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366ea0cd6081908e966a41c64d29c8 |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:46 a.m.