Triple
T14757745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Halliday |
E346773
|
entity |
| Predicate | workLocation |
P7
|
FINISHED |
| Object | Broadway |
unclear NED1
|
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: Broadway | Statement: [Richard Halliday, workLocation, Broadway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Broadway Context triple: [Richard Halliday, workLocation, Broadway]
-
A.
Broadway
Broadway is a major thoroughfare in Oakland, California, serving as a key commercial and transportation corridor through the city’s downtown.
-
B.
Broadway
Broadway is a major east–west thoroughfare in Vancouver, British Columbia, known as one of the city’s primary commercial and transit corridors.
-
C.
Broadway
Broadway is a major north–south thoroughfare on Chicago’s North Side known for its dense mix of shops, restaurants, and neighborhood commercial districts.
-
D.
Broadway
Broadway is a major thoroughfare that runs through the hamlet of Massapequa in Nassau County, New York.
-
E.
Broadway
Broadway is a major east–west thoroughfare in Monmouth County, New Jersey, serving as a locally known segment of County Route 537.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7ef0fd48190bd4a8af128ef274c |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0ced0e2c8190a13e3b43e4d35560 |
completed | May 8, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:30 a.m.