Triple
T4068090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascott |
E86376
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Ascott |
E86376
|
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: Ascott | Statement: [Ascott, hasName, Ascott]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ascott Context triple: [Ascott, hasName, Ascott]
-
A.
Ascott
chosen
Ascott is a small rural village located within the district of West Oxfordshire in Oxfordshire, England.
-
B.
Wyndham
Wyndham is a small, remote town in Western Australia's far north, known as one of the state's northernmost settlements and a gateway to the Kimberley region.
-
C.
Dorchester Collection
Dorchester Collection is a luxury hotel management company that owns and operates a portfolio of high-end, landmark hotels in major cities around the world.
-
D.
Brighton Resort
Brighton Resort is a popular ski and snowboard area in Utah known for its abundant snowfall, varied terrain, and family-friendly atmosphere.
-
E.
Halton Lodge
Halton Lodge is a residential area in Runcorn, Cheshire, England, known for its housing estates and local community amenities.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf8f33c8190a6afca1830f35485 |
completed | March 9, 2026, 4:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562b48fc481908547d51aae15e959 |
completed | March 14, 2026, 1:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.