Triple
T18637674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amanda Carrington |
E455595
|
entity |
| Predicate | hasFictionalWealthStatus |
P58963
|
FINISHED |
| Object | wealthy |
—
|
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: wealthy | Statement: [Amanda Carrington, hasFictionalWealthStatus, wealthy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalWealthStatus Context triple: [Amanda Carrington, hasFictionalWealthStatus, wealthy]
-
A.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
B.
hasFictionalProperty
chosen
Indicates that an entity possesses a property, attribute, or characteristic that exists only in a fictional or imaginary context.
-
C.
hasFictionalEconomicActivity
Indicates that an entity is involved in an economic activity that exists only in a fictional or imaginary context.
-
D.
isWealthy
Indicates that an entity possesses a high level of financial resources or assets relative to a given standard.
-
E.
hasPrivateWealth
Indicates that an entity possesses personal financial assets or wealth that are privately owned and not part of shared or public resources.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc9fa6c81909e1b988bdfb5ebcc |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.