Triple
T7999919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Spread Eagle Hotel, Thame |
E186219
|
entity |
| Predicate | isLocatedInArea |
P39182
|
FINISHED |
| Object | town centre of Thame |
—
|
LITERAL 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: town centre of Thame | Statement: [The Spread Eagle Hotel, Thame, isLocatedInArea, town centre of Thame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInArea Context triple: [The Spread Eagle Hotel, Thame, isLocatedInArea, town centre of Thame]
-
A.
isInArea
chosen
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
B.
isLocatedInAdministrativeArea
Indicates that one entity is situated within the geographic or jurisdictional boundaries of a specified administrative area (such as a city, county, state, or region).
-
C.
meetsInRegion
Indicates that two or more entities encounter or come together within a specified geographic or spatial region.
-
D.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- F. None of above.
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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c9b67988190a8a4a2c960017400 |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:17 p.m.