Triple
T36010434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fonthill Abbey |
E1041389
|
entity |
| Predicate | patronWealthSource |
P8003
|
FINISHED |
| Object | West Indian plantations |
—
|
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: West Indian plantations | Statement: [Fonthill Abbey, patronWealthSource, West Indian plantations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronWealthSource Context triple: [Fonthill Abbey, patronWealthSource, West Indian plantations]
-
A.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
B.
wealthSource
chosen
Indicates the relationship by which an entity obtains or derives its wealth from a particular source.
-
C.
patronageFrom
Indicates a relationship where support, sponsorship, or backing is provided to someone or something by a patron.
-
D.
nameBearerWealthSource
Indicates that the bearer of a particular name derives or is associated with a specific source of wealth.
-
E.
patron of
Indicates a supportive relationship in which one entity provides sponsorship, protection, or backing to another, often enabling its activities or development.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.