Triple

T19987414
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam Zuid E493969 entity
Predicate hasStationCode P1289 FINISHED
Object Asdz 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: Asdz | Statement: [Amsterdam Zuid, hasStationCode, Asdz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asdz
Context triple: [Amsterdam Zuid, hasStationCode, Asdz]
  • A. ASDZ chosen
    ASDZ is the station code used to identify Amsterdam Zuid railway station in the Netherlands.
  • B. ASZ
    ASZ is a German vehicle registration code formerly used for the town of Aue-Schwarzenberg in the Erzgebirgskreis district of Saxony.
  • C. Azd
    Azd is a prominent ancient Arab tribe, historically influential in the Arabian Peninsula and known as the lineage of several notable early Islamic figures.
  • D. Agdz
    Agdz is a small oasis town in southeastern Morocco that serves as a historic stopover and gateway along the Drâa Valley caravan route between Ouarzazate and the Sahara.
  • E. ZAZ
    ZAZ is the IATA airport code for Zaragoza Airport, a major civilian and military airfield serving the city of Zaragoza in northeastern Spain.
  • 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65fdd1a5c8190af756632aac38bf4 completed April 20, 2026, 5:18 p.m.
Created at: April 11, 2026, 3:29 p.m.