Triple
T34664651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Cane |
E890217
|
entity |
| Predicate | replacedPlayerAsStartingOpensideForAllBlacks |
P124194
|
FINISHED |
| Object | Richie McCaw |
—
|
NE NERFINISHED |
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: Richie McCaw | Statement: [Sam Cane, replacedPlayerAsStartingOpensideForAllBlacks, Richie McCaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedPlayerAsStartingOpensideForAllBlacks Context triple: [Sam Cane, replacedPlayerAsStartingOpensideForAllBlacks, Richie McCaw]
-
A.
replacedPlayer
Indicates that one player has been substituted out of play and replaced by another player.
-
B.
replacedInLineupBy
chosen
Indicates that one participant in a lineup is substituted or superseded by another participant in that same lineup.
-
C.
hasStartingPlayer
Indicates that a specific player is designated as the one who begins or takes the first turn in a game or activity.
-
D.
replacementPlayersUsed
Indicates that substitute or backup players were brought in to take the place of original players in a game or event.
-
E.
playedForStart
Indicates the time or date when an entity (typically a person) began playing for a particular team or organization.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 1, 2026, 2:04 a.m.