Triple
T33210460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neely Crenshaw |
E850141
|
entity |
| Predicate | relationshipWithCoach |
P187284
|
FINISHED |
| Object | complex |
—
|
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: complex | Statement: [Neely Crenshaw, relationshipWithCoach, complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithCoach Context triple: [Neely Crenshaw, relationshipWithCoach, complex]
-
A.
coachRelationship
Indicates a relationship in which one entity serves as a coach, providing guidance, training, or mentorship to another entity.
-
B.
associatedWithCoachRole
Indicates that an entity has a relationship involving the role or function of a coach, such as serving as, working as, or being linked to a coaching position.
-
C.
workedWithCoach
chosen
Indicates that an entity has received guidance, training, or collaboration from a coach in some capacity.
-
D.
influencedByCoach
Indicates that an entity’s performance, behavior, or development is affected or shaped by the guidance or actions of a coach.
-
E.
refinedIdentityUnderCoach
Indicates that an entity’s identity has been further developed or clarified through the guidance or influence of a coach.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.