Triple
T22621422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Langley Rose |
E558289
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Langley |
—
|
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: Langley | Statement: [Elizabeth Langley Rose, familyName, Langley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langley Context triple: [Elizabeth Langley Rose, familyName, Langley]
-
A.
Langley
Langley is a small coastal city on Whidbey Island in Washington State, known for its scenic waterfront, arts community, and tourism.
-
B.
Langley
Langley is the historical name for the English village now known as Kings Langley in Hertfordshire.
-
C.
Langley
Langley is a suburban area in Berkshire, England, situated near Slough and known for its residential neighborhoods and transport links into London.
-
D.
Langley
Langley is a residential area and housing estate forming part of the town of Middleton in Greater Manchester, England.
-
E.
Langley
Langley is a municipality in British Columbia, Canada, known for its suburban communities, agricultural lands, and role as part of Metro Vancouver’s Fraser Valley region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e39959481909e0ae67379435f95 |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 3 p.m.