Triple
T21054583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manoa |
E518675
|
entity |
| Predicate | hopesFor |
P128116
|
FINISHED |
| Object | God’s mercy on Samson |
—
|
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: God’s mercy on Samson | Statement: [Manoa, hopesFor, God’s mercy on Samson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hopesFor Context triple: [Manoa, hopesFor, God’s mercy on Samson]
-
A.
holderExpectation
chosen
Indicates that one entity has an expectation, belief, or anticipated outcome regarding another entity or situation.
-
B.
holdsFor
Indicates that a particular relationship or condition remains true over a specified interval or duration of time.
-
C.
hasPotential
Indicates that an entity possesses the capacity or possibility to develop, achieve, or exhibit a particular state, quality, or outcome in the future.
-
D.
wishMadeTo
Indicates that one entity has expressed a wish, desire, or hope directed toward another entity.
-
E.
anticipates
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7edb8481908e4dc7573f7fa98f |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:36 p.m.