Triple
T17087750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lousã |
E414642
|
entity |
| Predicate | distanceFromCoimbra |
P116447
|
FINISHED |
| Object | approximately 25 km southeast |
—
|
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: approximately 25 km southeast | Statement: [Lousã, distanceFromCoimbra, approximately 25 km southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCoimbra Context triple: [Lousã, distanceFromCoimbra, approximately 25 km southeast]
-
A.
distanceToCoimbra
chosen
Indicates the spatial distance between a given entity and the location of Coimbra.
-
B.
distanceFromLisbon
Indicates the measured spatial distance between a given entity’s location and the city of Lisbon.
-
C.
distanceFromPorto
Indicates the measured distance between a given place or entity and the city of Porto.
-
D.
distanceToLeiria
Indicates the spatial distance between a given entity and the location of Leiria.
-
E.
distanceToSalamanca
Indicates the spatial distance between a given entity and the location of Salamanca.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe92e488190b947287a968086d5 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.