Triple
T36588667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Butler Johnston |
E902601
|
entity |
| Predicate | hasWealthReflectedIn |
P186204
|
FINISHED |
| Object | Johnston–Felton–Hay House |
—
|
NE NERFINISHED |
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: Johnston–Felton–Hay House | Statement: [William Butler Johnston, hasWealthReflectedIn, Johnston–Felton–Hay House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWealthReflectedIn Context triple: [William Butler Johnston, hasWealthReflectedIn, Johnston–Felton–Hay House]
-
A.
hasPrivateWealth
Indicates that an entity possesses personal financial assets or wealth that are privately owned and not part of shared or public resources.
-
B.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
C.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
D.
isWealthy
Indicates that an entity possesses a high level of financial resources or assets relative to a given standard.
-
E.
usesWealthFor
Indicates that one entity directs or allocates its wealth or financial resources toward another entity or purpose.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:11 p.m.