Triple
T20225822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court Hunting Service |
E495374
|
entity |
| Predicate | servedClass |
P139310
|
FINISHED |
| Object | hereditary nobility of the Russian Empire |
—
|
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: hereditary nobility of the Russian Empire | Statement: [Court Hunting Service, servedClass, hereditary nobility of the Russian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedClass Context triple: [Court Hunting Service, servedClass, hereditary nobility of the Russian Empire]
-
A.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
B.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
-
C.
isServedFor
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
-
D.
serviceClass
Indicates the classification or category of service associated with or provided by an entity in the relationship.
-
E.
servedFrom
Indicates that something is provided, delivered, or made available from a particular source or location.
- 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_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. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:39 p.m.