Triple
T18460305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign Prince of Liechtenstein |
E451013
|
entity |
| Predicate | hasPrivateWealth |
P131739
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sovereign Prince of Liechtenstein, hasPrivateWealth, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrivateWealth Context triple: [Sovereign Prince of Liechtenstein, hasPrivateWealth, true]
-
A.
isWealthy
Indicates that an entity possesses a high level of financial resources or assets relative to a given standard.
-
B.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
C.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
D.
hasTrustFund
Indicates that an entity possesses or benefits from a trust fund established to hold and manage assets for them.
-
E.
wealthDescribedAs
Indicates that one entity’s wealth is characterized, portrayed, or expressed in terms of another entity or description.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7e65bc8190a824bce5b322c3de |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:33 a.m.