Triple
T19997519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonquel Jones |
E494232
|
entity |
| Predicate | reboundSpecialist |
P109237
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Jonquel Jones, reboundSpecialist, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reboundSpecialist Context triple: [Jonquel Jones, reboundSpecialist, yes]
-
A.
rebounderType
chosen
Indicates the specific role or category of a participant in a rebounding action or relationship.
-
B.
ownerAfterBreakup
Indicates which entity has ownership of something following the end of a romantic or partnership breakup.
-
C.
recovery
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
D.
recoveryBy
Indicates that one entity regains or restores something (such as health, function, or a resource) through the action, intervention, or influence of another entity.
-
E.
comebackWorkFor
Indicates that an entity returns to a previous workplace or employer to work again.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe6827481909469129feb9aad91 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:32 p.m.