Triple

T22509381
Position Surface form Disambiguated ID Type / Status
Subject Mapperley E556477 entity
Predicate locatedNear P294 FINISHED
Object Arnold 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: Arnold | Statement: [Mapperley, locatedNear, Arnold]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arnold
Context triple: [Mapperley, locatedNear, Arnold]
  • A. Arnold
    Arnold is a common English and German surname borne by numerous notable individuals across fields such as science, politics, sports, and the arts.
  • B. Arnold
    Arnold is a masculine given name of Germanic origin commonly used in various European and English-speaking countries.
  • C. Arnold
    Arnold is a small city located in Westmoreland County, Pennsylvania, in the United States.
  • D. Arnold chosen
    Arnold is a market town and suburb in the county of Nottinghamshire, England, situated to the northeast of Nottingham.
  • E. Arnold
    Arnold is a small mountain community in Calaveras County, California, known as a gateway to the Sierra Nevada with access to outdoor recreation and nearby state parks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e555edc81909ca803587dafd747 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15d5ebe5881908a22d519128415f2 completed April 29, 2026, 1:22 a.m.
Created at: April 16, 2026, 8:50 p.m.