Triple
T1886143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ware, Hertfordshire |
E39968
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | WARE |
E194909
|
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: WARE | Statement: [Ware, Hertfordshire, hasPostTown, WARE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WARE Context triple: [Ware, Hertfordshire, hasPostTown, WARE]
-
A.
Ware
Ware was the plaintiff in the landmark U.S. Supreme Court case Ware v. Hylton, which addressed the supremacy of federal treaties over conflicting state laws.
-
B.
Ware
chosen
Ware is a historic market town in Hertfordshire, England, known for its riverside setting on the River Lea and its long-standing role as a local commercial and coaching center.
-
C.
WD
WD is a consumer-facing brand of Western Digital known for its hard drives, solid-state drives, and other data storage products.
-
D.
WAS
WAS is the standard three-letter abbreviation used for the Washington Commanders NFL franchise.
-
E.
WAS
WAS is the station code for Washington, D.C.’s main intercity and commuter rail hub, Union Station.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb12032c881909cd93e3601906f48 |
completed | March 7, 2026, 5:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69addf63863881908efd8010db14b8a8 |
completed | March 8, 2026, 8:43 p.m. |
Created at: March 4, 2026, 7:34 p.m.