Triple
T32093502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richie Mo'unga |
E819663
|
entity |
| Predicate | alsoPlaysPosition |
P11751
|
FINISHED |
| Object | first five-eighth |
—
|
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: first five-eighth | Statement: [Richie Mo'unga, alsoPlaysPosition, first five-eighth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoPlaysPosition Context triple: [Richie Mo'unga, alsoPlaysPosition, first five-eighth]
-
A.
playsInPosition
chosen
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
B.
coachPositionPlayed
Indicates the role or position a coach played (typically as a player) in the sport they are associated with.
-
C.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
D.
includesPositionPlayers
Indicates that a group, team, or lineup contains players assigned to specific positions.
-
E.
alsoPlayed
Indicates that the same entity participated in or performed in an additional role, work, or context beyond the one already specified.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b63f9da88190975712a5644500c7 |
completed | May 3, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:25 a.m.