Triple
T17806397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heythrop Park |
E444571
|
entity |
| Predicate | operatedAsHotelFrom |
P4445
|
FINISHED |
| Object | early 21st century |
—
|
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: early 21st century | Statement: [Heythrop Park, operatedAsHotelFrom, early 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsHotelFrom Context triple: [Heythrop Park, operatedAsHotelFrom, early 21st century]
-
A.
operatedAs
chosen
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
B.
operatedFrom
Indicates that an entity conducted its activities or operations starting from or based at a particular location or source.
-
C.
operatedAsNameUntil
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
-
D.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
E.
hadStationHotel
Indicates that a railway station possessed or was associated with a hotel facility serving its passengers or operations.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e488044cdc8190a09a2265c8a86475 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.