Triple
T19648042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zelda Fuller |
E471731
|
entity |
| Predicate | resourceful |
P136820
|
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: [Zelda Fuller, resourceful, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceful Context triple: [Zelda Fuller, resourceful, true]
-
A.
richIn
Indicates that something contains a high amount or concentration of a particular substance, quality, or resource.
-
B.
isResourcePoor
Indicates that an entity lacks sufficient resources (such as money, materials, or capacity) to meet its needs or perform effectively.
-
C.
secondaryResource
Indicates that a resource serves as a secondary, supporting, or auxiliary resource in relation to a primary one.
-
D.
traditionalResource
Indicates that one entity is a resource or practice that has been passed down through tradition and is recognized as part of a longstanding cultural or customary system used by another entity.
-
E.
usedResource
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64126cea88190a1a6929f46de4686 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.