Triple
T9919040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulsa |
E185942
|
entity |
| Predicate | hasHistoricDistrict |
P295
|
FINISHED |
| Object | Greenwood District |
E201304
|
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: Greenwood District | Statement: [Tulsa, hasHistoricDistrict, Greenwood District]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Greenwood District Context triple: [Tulsa, hasHistoricDistrict, Greenwood District]
-
A.
Greenwood District
chosen
The Greenwood District is a historic African American neighborhood in Tulsa, Oklahoma, once known as "Black Wall Street" and the site of the 1921 Tulsa Race Massacre.
-
B.
Church Hill
Church Hill is a notable historic and cultural landmark area in the Latvian city of Daugavpils.
-
C.
Greenwood Historic District
Greenwood Historic District is a nationally recognized historic area in Greenwood, Mississippi, noted for its well-preserved architecture and significance in the region’s commercial and cultural development.
-
D.
Greenwood
Greenwood is a residential neighborhood within the town of Bicester in Oxfordshire, England.
-
E.
Greenwood
Greenwood is a residential neighborhood within the city of Warwick in the U.S. state of Rhode Island.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb5685a908190ab3e55b9bf9613f6 |
completed | April 2, 2026, 12:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d20df77f208190b550b888bf7b55ea |
completed | April 5, 2026, 7:23 a.m. |
Created at: March 30, 2026, 8:42 p.m.