Triple
T30000295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Guarda |
E762147
|
entity |
| Predicate | highestCityIn |
P181150
|
FINISHED |
| Object | Portugal |
—
|
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: Portugal | Statement: [municipality of Guarda, highestCityIn, Portugal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestCityIn Context triple: [municipality of Guarda, highestCityIn, Portugal]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
nearHighestPeakOf
Indicates that one entity is located close to the highest peak of another referenced geographic or topographic feature.
-
C.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
-
D.
hasHighestCity
Indicates that one entity possesses or contains the city with the greatest value according to some ranking criterion (e.g., highest population, elevation, or status) among a set of cities.
-
E.
hasHighestElevationsOf
Indicates that one entity possesses the greatest elevation values (e.g., altitudes or heights) compared to another entity or set of entities.
- F. None of above. chosen
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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 29, 2026, 6:41 p.m.