Triple
T4432729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydia |
E95370
|
entity |
| Predicate | reputedSourceOfWealth |
P8003
|
FINISHED |
| Object | gold from the Pactolus River |
—
|
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: gold from the Pactolus River | Statement: [Lydia, reputedSourceOfWealth, gold from the Pactolus River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reputedSourceOfWealth Context triple: [Lydia, reputedSourceOfWealth, gold from the Pactolus River]
-
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.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
D.
richIn
Indicates that something contains a high amount or concentration of a particular substance, quality, or resource.
-
E.
managesWealthFor
Indicates that one entity is responsible for overseeing, controlling, or administering the financial assets or wealth of another entity.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3556cd83881908547aa311c4f17fa |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.