Triple
T15509396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redding federal courthouse |
E368665
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Redding, California |
E27620
|
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: Redding, California | Statement: [Redding federal courthouse, locatedIn, Redding, California]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Redding, California Context triple: [Redding federal courthouse, locatedIn, Redding, California]
-
A.
Redding
Redding is a surname most famously associated with legendary American soul singer Otis Redding and his musically inclined family.
-
B.
Redding
Redding is a village in central Scotland, situated within the Falkirk council area and historically associated with coal mining.
-
C.
Redding
Redding is a small city located in Ringgold County in the southern part of the U.S. state of Iowa.
-
D.
Redding
chosen
Redding is a mid-sized city in Northern California known as a regional hub for outdoor recreation, with access to Shasta Lake, the Sacramento River, and nearby national forests.
-
E.
Redding
Redding was the former name of Elizabeth City, a historic riverfront community in northeastern North Carolina.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03fd008708190a3657863eb9ac626 |
completed | April 16, 2026, 1:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff36702ebc81908d6a00243865de61 |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 10, 2026, 3:55 a.m.