Triple
T21382660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiesloch |
E527400
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Amarante |
—
|
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: Amarante | Statement: [Wiesloch, twinTown, Amarante]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amarante Context triple: [Wiesloch, twinTown, Amarante]
-
A.
Amarante
chosen
Amarante is a Portuguese wine subregion within Vinho Verde, known for producing fresh, often slightly sparkling white wines as well as some reds and rosés.
-
B.
Amarante
Amarante is a Portuguese surname most notably associated with Brazilian musician and songwriter Rodrigo Amarante.
-
C.
Vimeiro
Vimeiro is a village in western Portugal historically notable as the site of a major 1808 battle during the Peninsular War.
-
D.
Alverca
Alverca is a Portuguese football club known for having been an early stepping stone in the professional career of midfielder Deco.
-
E.
Góis
Góis is a small municipality in central Portugal known for its mountainous landscapes, river beaches, and traditional schist villages.
- 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0d1fa1c8190b3374e0bb3a971fc |
completed | April 22, 2026, 11:28 a.m. |
Created at: April 16, 2026, 5:12 p.m.