Triple

T9598761
Position Surface form Disambiguated ID Type / Status
Subject Highway 1 (Tel Aviv–Jerusalem) corridor E231796 entity
Predicate hasBeenUpgraded P63116 FINISHED
Object widening projects LITERAL 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: widening projects | Statement: [Highway 1 (Tel Aviv–Jerusalem) corridor, hasBeenUpgraded, widening projects]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBeenUpgraded
Context triple: [Highway 1 (Tel Aviv–Jerusalem) corridor, hasBeenUpgraded, widening projects]
  • A. wasUpgradedFor
    Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
  • B. hasUpgrade
    Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
  • C. upgradedBy chosen
    Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
  • D. partlyUpgradedTo
    Indicates that an entity has undergone an incomplete or partial upgrade to another specified state, version, or configuration.
  • E. openedAsUpgradeOf
    Indicates that one entity was opened specifically as an upgraded or improved replacement of another entity.
  • F. None of above.

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_69ca8484838c8190b2049199d22fef70 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9a366d3481908db62e476958eafe completed April 1, 2026, 10:20 p.m.
PD Predicate disambiguation batch_69ccd5a359788190b24f82399489f7fe completed April 1, 2026, 8:21 a.m.
Created at: March 30, 2026, 8:07 p.m.