Triple
T20225834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court Hunting Service |
E495374
|
entity |
| Predicate | usedResources |
P22475
|
FINISHED |
| Object | imperial hunting reserves |
—
|
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: imperial hunting reserves | Statement: [Court Hunting Service, usedResources, imperial hunting reserves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedResources Context triple: [Court Hunting Service, usedResources, imperial hunting reserves]
-
A.
usedResource
chosen
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
-
B.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
C.
usedEquipmentFrom
Indicates that one entity has utilized or operated equipment that originated from or was provided by another entity.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
usedRite
Indicates that an entity performed, followed, or applied a particular rite or ritual in some context.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd9c1f4819092a98f5fa84fb795 |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.