Triple

T37334951
Position Surface form Disambiguated ID Type / Status
Subject Fortville, Indiana E926864 entity
Predicate adjacentMetropolitanArea P193226 FINISHED
Object Indianapolis, Indiana 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: Indianapolis, Indiana | Statement: [Fortville, Indiana, adjacentMetropolitanArea, Indianapolis, Indiana]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: adjacentMetropolitanArea
Context triple: [Fortville, Indiana, adjacentMetropolitanArea, Indianapolis, Indiana]
  • A. adjacentMajorCity
    Indicates that one major city is geographically next to or directly bordering another major city.
  • B. metropolitanAreaWith
    Indicates that one entity is a metropolitan area that includes, is associated with, or encompasses the other entity.
  • C. isMetropolitanArea
    Indicates that a given area functions as a major urban center and its surrounding region, typically characterized by high population density and integrated economic and social activities.
  • D. belongsToMetropolitanRegion
    Indicates that one geographic or administrative area is part of, or included within, a larger metropolitan region.
  • E. metropolitanOf
    Indicates that one place serves as the primary metropolitan center or core urban area for another place or region.
  • 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_69f76eb4e8a881908bd40da28f36fc7e completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd3a69f1e08190a11aed015bff0858 completed May 8, 2026, 1:20 a.m.
PD Predicate disambiguation batch_69fd39124180819080ca7911d3515d6d completed May 8, 2026, 1:14 a.m.
PDg Predicate description generation batch_69fd3a6905b88190ae12b43576f4cc63 completed May 8, 2026, 1:20 a.m.
Created at: May 3, 2026, 4:16 p.m.