Triple

T6993078
Position Surface form Disambiguated ID Type / Status
Subject China, Maine E162130 entity
Predicate hasZIPCodeArea P920 FINISHED
Object South China, Maine E162130 NE 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: South China, Maine | Statement: [China, Maine, hasZIPCodeArea, South China, Maine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: South China, Maine
Context triple: [China, Maine, hasZIPCodeArea, South China, Maine]
  • A. China, Maine chosen
    China, Maine is a small rural town in central Maine known for its lakes, including China Lake, and its quiet residential character.
  • B. Strong, Maine
    Strong, Maine is a small rural town in western Maine known historically for its lumber and toothpick manufacturing industries.
  • C. Freedom, Maine
    Freedom, Maine is a small rural town in central Maine known for its scenic countryside and tight-knit community.
  • D. Southern Lau
    Southern Lau is a dialectal variety of the Lau language spoken on Malaita in the Solomon Islands.
  • E. Peru, Maine
    Peru, Maine is a small rural town in Oxford County known for its scenic western Maine landscape and close-knit community.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c68856d7808190ab33ee914640281b completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dbc30fdc81909244d83c8178755c completed March 27, 2026, 7:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69c76a161f088190bbc3c4e2815fa929 completed March 28, 2026, 5:41 a.m.
Created at: March 27, 2026, 2:32 p.m.