Triple
T509858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament of Scotland |
E10582
|
entity |
| Predicate | estate |
P14553
|
FINISHED |
| Object | clergy |
—
|
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: clergy | Statement: [Parliament of Scotland, estate, clergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estate Context triple: [Parliament of Scotland, estate, clergy]
-
A.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
-
B.
nobleEstate
Indicates that an entity is a noble’s estate or property associated with nobility.
-
C.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
D.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
E.
realEstateCategory
Indicates the classification of a property into a specific type or category within real estate (e.g., residential, commercial, industrial).
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f164a9d48190b525a97b5c06ffe2 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2edfe236481909901cc7d4281b33c |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebbd70481908b462296671de67b |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.