Triple

T18644659
Position Surface form Disambiguated ID Type / Status
Subject Lindsay Corporation E455772 entity
Predicate brand P1500 FINISHED
Object Road Zipper System 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: Road Zipper System | Statement: [Lindsay Corporation, brand, Road Zipper System]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Road Zipper System
Context triple: [Lindsay Corporation, brand, Road Zipper System]
  • A. Road Zipper System chosen
    Road Zipper System is a movable barrier and lane management solution used on highways and bridges to dynamically reconfigure traffic lanes and improve safety and congestion.
  • B. Zipper
    Zipper was the codename for a planned British amphibious operation to recapture Malaya from Japanese control near the end of World War II.
  • C. ZIPLO
    ZIPLO is an industrial and business zone located in the municipality of Plan-les-Ouates in the canton of Geneva, Switzerland.
  • D. Zips
    Zips is the nickname for the University of Akron's athletic teams, most prominently used for its NCAA Division I football program.
  • E. Zips
    Zips is a historical region in present-day Slovakia known for its significant Carpathian German (Zipser) community and medieval towns.
  • 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_69d8d38ea1e88190997e9b231190ba6f completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5500c36188190bfdd7aca73f3c006 completed April 19, 2026, 9:58 p.m.
Created at: April 10, 2026, 11:47 a.m.