Triple
T18339175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montemor-o-Velho |
E439354
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Figueira da Foz |
—
|
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: Figueira da Foz | Statement: [Montemor-o-Velho, near, Figueira da Foz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Figueira da Foz Context triple: [Montemor-o-Velho, near, Figueira da Foz]
-
A.
Figueira da Foz
chosen
Figueira da Foz is a coastal Portuguese city at the mouth of the Mondego River, known for its wide sandy beaches and seaside tourism.
-
B.
Figueira da Horta
Figueira da Horta is a small village located on the island of Maio in Cape Verde.
-
C.
Foz do Arelho
Foz do Arelho is a coastal village in Portugal known for its scenic beach and lagoon, popular for swimming, water sports, and seaside tourism.
-
D.
Porto-Campanhã
Porto-Campanhã is the main railway station in Porto, Portugal, serving as a central hub for long-distance and regional train services across the country.
-
E.
Porto de Mós
Porto de Mós is a Portuguese town and municipality known for its hilltop castle and location near the limestone landscapes and caves of central Portugal.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ed07db48190a15e957c96b1c5bf |
completed | April 19, 2026, 5:20 p.m. |
Created at: April 10, 2026, 10:37 a.m.