Triple

T24956528
Position Surface form Disambiguated ID Type / Status
Subject MEMHUS E624486 entity
Predicate cityComponent P30278 FINISHED
Object MEM (for Memphis)
MEM (for Memphis) is the commonly used abbreviation for the city of Memphis, Tennessee, in contexts such as transportation, sports, and regional identification.
 E1658185 NE FINISHED

How this triple was built (3 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: MEM (for Memphis) | Statement: [MEMHUS, cityComponent, MEM (for Memphis)]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: MEM (for Memphis)
Triple: [MEMHUS, cityComponent, MEM (for Memphis)]
Generated description
MEM (for Memphis) is the commonly used abbreviation for the city of Memphis, Tennessee, in contexts such as transportation, sports, and regional identification.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: cityComponent
Context triple: [MEMHUS, cityComponent, MEM (for Memphis)]
  • A. urbanComponent chosen
    Indicates that something functions as a constituent part or element within an urban area or city system.
  • B. cityFunction
    Indicates the primary role, purpose, or functional classification associated with a city (e.g., administrative, commercial, industrial, cultural).
  • C. cityService
    Indicates that a service is provided by, operates within, or is administered by a particular city.
  • D. cityhoodBy
    Indicates that an entity attained the status of a city through the action, decision, or authority of the referenced agent or process.
  • E. city2
    Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
  • F. None of above.

Provenance (6 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_69e2ff23a3a88190b1b9743fe5e15f94 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f424044cf8819092105c93ceba3b9c completed May 1, 2026, 3:54 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10334e44748190a6342b9888ee76d5 completed May 22, 2026, 10:43 a.m.
NEDg Description generation batch_6a103420ed908190b7be8e1a8b82a85c completed May 22, 2026, 10:46 a.m.
NED2 Entity disambiguation (via description) batch_6a1034aa0ed881909d877e1d9159b9d2 completed May 22, 2026, 10:49 a.m.
PD Predicate disambiguation batch_69f4210130d08190ae30b7943f7a0bbc completed May 1, 2026, 3:41 a.m.
Created at: April 18, 2026, 5:57 a.m.