Triple

T29648584
Position Surface form Disambiguated ID Type / Status
Subject Tamu E756071 entity
Predicate hasNearbyIndianTown P120858 FINISHED
Object Moreh 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: Moreh | Statement: [Tamu, hasNearbyIndianTown, Moreh]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearbyIndianTown
Context triple: [Tamu, hasNearbyIndianTown, Moreh]
  • A. nearbyIndianTown chosen
    Indicates that one location is a town in India situated close to the referenced place.
  • B. hasNearbyTown
    Indicates that one location has a town situated close to it in geographic proximity.
  • C. hasNearbyTownType
    Indicates that one entity has, in its vicinity, a town of a specified type or classification.
  • D. hasNearbyCityFunction
    Indicates that one entity serves as a nearby urban center or city-like service hub for another entity.
  • E. hasNearbyCityArea
    Indicates that one area is geographically close to or adjacent to a city area.
  • 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_69f0ef89d2c88190a6d0d5116ccd7cc9 completed April 28, 2026, 5:34 p.m.
NER Named-entity recognition batch_69fe5ec9028081909ae3d6fbe2f4cbbc completed May 8, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69fe5e1d715881909fc516fafc707644 completed May 8, 2026, 10:05 p.m.
Created at: April 28, 2026, 6:51 p.m.