Triple
T9642743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brentwood |
E233114
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Langdon |
E810626
|
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: Langdon | Statement: [Brentwood, adjacentTo, Langdon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langdon Context triple: [Brentwood, adjacentTo, Langdon]
-
A.
Langdon
Langdon is a given name that has been used as a masculine first name, notably in American contexts.
-
B.
Langdon
Langdon is a small village and civil parish located within the Dover District of Kent, England.
-
C.
Langdon
chosen
Langdon is a residential neighborhood in Northeast Washington, D.C., known for its tree-lined streets, parks, and proximity to the Bladensburg Road NE corridor.
-
D.
Leland
Leland is a masculine given name of English origin, historically associated with figures such as American industrialist and Stanford University founder Leland Stanford.
-
E.
Langdon Page
Langdon Page is an editor known for working on content related to Russian opposition leader Alexei Navalny.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b7cda388190a38f96d78085f404 |
completed | April 1, 2026, 10:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18252c1cc81908d33c9c55d645fbf |
completed | April 4, 2026, 9:27 p.m. |
Created at: March 30, 2026, 8:12 p.m.