Triple
T21945995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniel Plainview |
E541933
|
entity |
| Predicate | characterStatusByEnd |
P110763
|
FINISHED |
| Object | wealthy but isolated |
—
|
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 but isolated | Statement: [Daniel Plainview, characterStatusByEnd, wealthy but isolated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterStatusByEnd Context triple: [Daniel Plainview, characterStatusByEnd, wealthy but isolated]
-
A.
featuresCharacterWithStatus
Indicates that something (such as a work or scene) includes a character who has a specified status or condition.
-
B.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
C.
characterStatusInStory
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
D.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
E.
titleCharacterState
chosen
Indicates the state or condition a character is in within the context of a specific title or work.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12427c2b48190949c41bd3be2d9f3 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:57 p.m.