Triple

T15822001
Position Surface form Disambiguated ID Type / Status
Subject Alcántara E383635 entity
Predicate hasLandmark P105 FINISHED
Object Alcántara Bridge E81287 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: Alcántara Bridge | Statement: [Alcántara, hasLandmark, Alcántara Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alcántara Bridge
Context triple: [Alcántara, hasLandmark, Alcántara Bridge]
  • A. Puente de Alcántara chosen
    Puente de Alcántara is a historic Roman stone arch bridge spanning the Tagus River at Toledo, Spain, renowned for its medieval towers and role as a key entrance to the old city.
  • B. Granada Bridge
    Granada Bridge is a vehicular bridge in Ormond Beach, Florida, that spans the Halifax River as part of State Road 40.
  • C. Puente de Aragón
    Puente de Aragón is a road bridge in Valencia, Spain, that spans the Turia River and connects key districts of the city.
  • D. Valentré Bridge
    Valentré Bridge is a 14th-century fortified stone arch bridge in Cahors, France, renowned for its medieval military architecture and associated legends.
  • E. Puente Zaragoza
    Puente Zaragoza is a bridge spanning the Santa Catarina River, serving as a key transportation link in the surrounding region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0c4a887d881908f74a1fcba390727 completed April 16, 2026, 11:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffa93be478819099908e7242f532d7 completed May 9, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:49 a.m.