Triple
T38431571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tahiti national rugby union team |
E903816
|
entity |
| Predicate | governsPlayerBase |
P51793
|
FINISHED |
| Object | amateur 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: amateur players | Statement: [Tahiti national rugby union team, governsPlayerBase, amateur players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsPlayerBase Context triple: [Tahiti national rugby union team, governsPlayerBase, amateur players]
-
A.
governsPlayersFrom
Indicates that an entity exercises authority or control over players originating from a specified source or group.
-
B.
governsPlayerPathwayFor
Indicates that one entity controls or determines the developmental or progression pathway followed by a player.
-
C.
gameplayBasis
Indicates that one entity serves as the core mechanic, structure, or inspiration upon which another entity’s gameplay is designed or derived.
-
D.
playerBaseSize
Indicates the size or capacity of a player's base in a game or simulation context.
-
E.
regulatesPlayerSelection
chosen
Indicates that an entity sets or enforces rules or constraints governing how players are chosen or selected.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.