Triple
T4371422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathan Ford |
E98904
|
entity |
| Predicate | statusInLeverageRedemption |
P55825
|
FINISHED |
| Object | absent but referenced |
—
|
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: absent but referenced | Statement: [Nathan Ford, statusInLeverageRedemption, absent but referenced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInLeverageRedemption Context triple: [Nathan Ford, statusInLeverageRedemption, absent but referenced]
-
A.
allowsRedemptionFor
Indicates that one party grants another the right or ability to redeem something (such as a benefit, asset, or offer) under specified conditions.
-
B.
redeemabilityEndedReason
Indicates the reason why the ability to redeem something (e.g., a product, offer, or asset) has ended.
-
C.
redeemabilityEndedUnder
Indicates that the period or conditions under which something could be redeemed have come to an end under a specified context, rule, or authority.
-
D.
redeemabilityChangedTo
Indicates that the redeemability status of something has been updated or changed to a new specified state.
-
E.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521dffbc8190b9300a7f4f64bdc0 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:17 p.m.