Triple
T20338194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince’s Lodging, Newmarket (designs) |
E495669
|
entity |
| Predicate | intendedOccupant |
P139748
|
FINISHED |
| Object | English royal court |
—
|
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: English royal court | Statement: [Prince’s Lodging, Newmarket (designs), intendedOccupant, English royal court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedOccupant Context triple: [Prince’s Lodging, Newmarket (designs), intendedOccupant, English royal court]
-
A.
laterOccupant
Indicates that one entity occupied or held a position in a place or role after another entity had previously done so.
-
B.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
-
C.
formerOccupant
Indicates that an entity previously occupied a position, role, or place but no longer does so.
-
D.
occupiedFrom
Indicates that an entity is in use or inhabited starting from a specified point in time.
-
E.
occupants
Indicates that certain entities are currently inhabiting, residing in, or using a particular place, space, or object.
- F. None of above. chosen
Provenance (4 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678332bd08190a83880fb6aa32e08 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:23 a.m.