Triple
T1535437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya Moore |
E32538
|
entity |
| Predicate | reasonForHiatus |
P15987
|
FINISHED |
| Object | focus on criminal justice reform and family |
—
|
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: focus on criminal justice reform and family | Statement: [Maya Moore, reasonForHiatus, focus on criminal justice reform and family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForHiatus Context triple: [Maya Moore, reasonForHiatus, focus on criminal justice reform and family]
-
A.
reasonForDiscontinuation
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
B.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
-
C.
postponementReason
Indicates the reason or cause for which an event, action, or decision has been delayed or rescheduled.
-
D.
reasonForRelease
Indicates the cause, justification, or circumstance that led to an entity being released.
-
E.
reasonForLeaving
chosen
Indicates the cause, motivation, or circumstance that led an entity to depart or discontinue an association, position, or place.
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a915f323bc8190aa757142c225e0ae |
completed | March 5, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69a907b046448190be8ea4d7b20255f7 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.