Triple
T22575798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get By |
E544387
|
entity |
| Predicate | mayExplore |
P148798
|
FINISHED |
| Object | financial hardship |
—
|
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: financial hardship | Statement: [Get By, mayExplore, financial hardship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayExplore Context triple: [Get By, mayExplore, financial hardship]
-
A.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
B.
exploresFor
Indicates that one entity actively investigates or searches within or on behalf of another entity, typically to discover or obtain something for that other entity’s benefit.
-
C.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically to discover or learn more about it.
-
D.
explorationBy
Indicates a relationship where one entity conducts or performs exploration directed at or involving another entity.
-
E.
mayExperience
Indicates that an entity is capable of undergoing, feeling, or being subject to a particular event, state, or condition.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15fecf1c8819091a05f2a1b93ca8a |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:53 p.m.