Triple
T16757795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candler |
E407253
|
entity |
| Predicate | associatedWithHistoricWealth |
P31592
|
FINISHED |
| Object | Coca-Cola fortune |
—
|
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: Coca-Cola fortune | Statement: [Candler, associatedWithHistoricWealth, Coca-Cola fortune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHistoricWealth Context triple: [Candler, associatedWithHistoricWealth, Coca-Cola fortune]
-
A.
historicallyRich
Indicates that an entity possesses significant historical depth, importance, or a wealth of notable past events and heritage.
-
B.
economicLegacy
Indicates how past economic activities, policies, or conditions continue to shape or influence present and future economic outcomes or structures.
-
C.
associatedWithHistoricHome
Indicates a relationship in which an entity is connected or linked in some relevant way to a historic home.
-
D.
hasWealthType
chosen
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
E.
inheritsWealth
Indicates that one entity receives wealth or assets passed down from another, typically after the latter’s death.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abea156c8190a5ee6d0028471810 |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.