Triple

T13521133
Position Surface form Disambiguated ID Type / Status
Subject Mexican Federal Highway 40 E322896 entity
Predicate segmentKnownFor P110087 FINISHED
Object mountainous terrain 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: mountainous terrain | Statement: [Mexican Federal Highway 40, segmentKnownFor, mountainous terrain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: segmentKnownFor
Context triple: [Mexican Federal Highway 40, segmentKnownFor, mountainous terrain]
  • A. namedForKnownFor
    Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
  • B. underlyingKnownFor
    Indicates that one entity is fundamentally or primarily recognized as the basis or main reason for another entity’s notability or fame.
  • C. laterKnownFor
    Indicates that an entity became recognized or notable for something at a later time than the context or event currently being referred to.
  • D. alsoKnownFor
    Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
  • E. knownIn
    Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
  • F. None of above. chosen

Provenance (4 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_69d80766a21881909f21a1b7421d3b8a completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafa3df0c8190804174695587f0ea completed April 12, 2026, 2:43 p.m.
PD Predicate disambiguation batch_69dbae0b63748190b5e207f84b2532ea completed April 12, 2026, 2:36 p.m.
PDg Predicate description generation batch_69dbaee128d88190b097be17fdd2f92b completed April 12, 2026, 2:40 p.m.
Created at: April 9, 2026, 9:44 p.m.