Triple

T16972914
Position Surface form Disambiguated ID Type / Status
Subject Madrid metropolitan area E411731 entity
Predicate hasMotorway P385 FINISHED
Object A-2 E1070570 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: A-2 | Statement: [Madrid metropolitan area, hasMotorway, A-2]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A-2
Context triple: [Madrid metropolitan area, hasMotorway, A-2]
  • A. A-2 chosen
    The A-2 is a major Spanish motorway that connects Madrid with northeastern regions such as Zaragoza and Barcelona, forming part of the country’s primary eastward transport corridor.
  • B. 2A
    2A is a state highway designation used for an auxiliary route of Massachusetts Route 2 that serves local traffic through several cities and towns in the state.
  • C. A-23
    A-23 is the internal station code assigned to Warsaw's Młociny metro station on Line M1.
  • D. A22
    A22 is a major Portuguese motorway, commonly known as Via do Infante, that runs across the Algarve region in southern Portugal.
  • E. A-3
    The A-3 is a major Spanish motorway that connects Madrid with Valencia and the eastern Mediterranean coast.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d0ae47f08190a13e98d20aba7f16 completed April 18, 2026, 6:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00d4738fbc819099e8281ebc777091 completed May 10, 2026, 6:54 p.m.
Created at: April 10, 2026, 5:31 a.m.