Triple
T7954300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santee |
E184692
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Poway |
E148167
|
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: Poway | Statement: [Santee, adjacentTo, Poway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Poway Context triple: [Santee, adjacentTo, Poway]
-
A.
Poway
chosen
Poway is a suburban city in Southern California known for its residential communities, parks, and location inland from the San Diego coast.
-
B.
Warley
Warley is a locality within the Brentwood Borough of Essex, England, known primarily as a residential suburb with historical military and institutional connections.
-
C.
Pooncarie
Pooncarie is a small rural town in far south-west New South Wales, Australia, known for its remote outback setting and proximity to the Darling River.
-
D.
Parchen
Parchen is a village and district of the town of Genthin in the German state of Saxony-Anhalt.
-
E.
Pawley
Pawley is a surname and variant spelling of Pauley, borne by various individuals and families.
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b5f74308190aa63a22c3d5feacc |
completed | March 31, 2026, 3:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe05d89a08190ae5bd4092d007442 |
completed | March 31, 2026, 2:55 p.m. |
Created at: March 30, 2026, 5:11 p.m.