Triple
T33210556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coach Eddie Rake |
E850143
|
entity |
| Predicate | relationshipWithPlayers |
P72605
|
FINISHED |
| Object | admired by former players |
—
|
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: admired by former players | Statement: [Coach Eddie Rake, relationshipWithPlayers, admired by former players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithPlayers Context triple: [Coach Eddie Rake, relationshipWithPlayers, admired by former players]
-
A.
relationshipToPlayer
Indicates the type of personal or social connection an entity has with the player.
-
B.
associatedWithPlayers
chosen
Indicates a relationship in which one or more players are connected, linked, or otherwise involved with the referenced entity.
-
C.
playerRelations
Indicates the nature or status of the relationship between players, such as alliances, rivalries, or other interpersonal dynamics.
-
D.
playedWith
Indicates that one entity engaged in play or a playful activity together with another entity.
-
E.
playsWith
Indicates that one entity engages in play or recreational activity together with another entity.
- 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.