Triple

T13820587
Position Surface form Disambiguated ID Type / Status
Subject Peraea E332123 entity
Predicate hasAlternateName P39 FINISHED
Object Perea E66078 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: Perea | Statement: [Peraea, hasAlternateName, Perea]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Perea
Context triple: [Peraea, hasAlternateName, Perea]
  • A. Perea chosen
    Perea was a region east of the Jordan River in the early 1st century CE, forming part of Herod Antipas’s tetrarchy within the broader territory of Roman-era Judea.
  • B. Cedros
    Cedros is a municipality located in the Francisco Morazán Department of central Honduras.
  • C. Cedros
    Cedros is a civil parish on Faial Island in Portugal’s Azores archipelago, known for its rural landscape and traditional Azorean character.
  • D. Olmos
    Olmos is a surname most prominently associated with American actor and director Edward James Olmos, known for his roles in film and television.
  • E. Palo Cedro
    Palo Cedro is a small unincorporated community in Northern California known for its rural character and proximity to the city of Redding.
  • 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_69d81c59f8808190a851bc56afdc55e9 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0282d4d08190b754cda7683408c4 completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c70454a8819097b5e5091f84be33 completed May 3, 2026, 10:07 p.m.
Created at: April 9, 2026, 10:12 p.m.