Triple
T5856299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilmington Blue Rocks |
E130161
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Wilmington |
E39070
|
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: Wilmington | Statement: [Wilmington Blue Rocks, city, Wilmington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wilmington Context triple: [Wilmington Blue Rocks, city, Wilmington]
-
A.
Wilmington
Wilmington is a suburban town in northeastern Massachusetts, United States, located within the Greater Boston area.
-
B.
Wilmington
Wilmington is a village and civil parish in the Dartford district of Kent, England, situated near the town of Swanley.
-
C.
Wilmington
Wilmington is a historic harbor-area neighborhood in the city of Los Angeles, California, known for its proximity to the Port of Los Angeles and its industrial and maritime character.
-
D.
Wilmington
Wilmington is the largest city in the U.S. state of Delaware, known as a regional financial and corporate hub.
-
E.
Wilmington
chosen
Wilmington is a historic port city in southeastern North Carolina known for its riverfront, nearby Atlantic beaches, and well-preserved downtown district.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03555cd6081908b0307decd60d2bc |
completed | March 22, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1134931c48190b4a849c8f16723e3 |
completed | March 23, 2026, 10:17 a.m. |
Created at: March 22, 2026, 3:55 p.m.