Triple
T22567806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hope |
E557997
|
entity |
| Predicate | canBeExperiencedBy |
P138332
|
FINISHED |
| Object | individuals |
—
|
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: individuals | Statement: [Hope, canBeExperiencedBy, individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeExperiencedBy Context triple: [Hope, canBeExperiencedBy, individuals]
-
A.
mayExperience
chosen
Indicates that an entity is capable of undergoing, feeling, or being subject to a particular event, state, or condition.
-
B.
providesExperienceOf
Indicates that one entity enables or delivers the experience of another entity to someone or something.
-
C.
experiencedByCharacter
Indicates that a particular event, situation, or emotion is undergone or lived through by a specific character.
-
D.
gaveFirsthandExperienceOf
Indicates that one entity directly provided another entity with personal, firsthand experience of something, rather than secondhand or indirect knowledge.
-
E.
providesExposureTo
Indicates that one entity gives another entity the opportunity to be seen, noticed, or become known by a particular audience, environment, or set of influences.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fabb9f081908c33c8e2ddf18047 |
completed | April 29, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:52 p.m.