Triple
T33237710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lions |
E850875
|
entity |
| Predicate | teamSelectionFrom |
P72353
|
FINISHED |
| Object | England national rugby union team 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: England national rugby union team players | Statement: [Lions, teamSelectionFrom, England national rugby union team players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamSelectionFrom Context triple: [Lions, teamSelectionFrom, England national rugby union team players]
-
A.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
B.
teamSelectionAuthority
Indicates that an entity has the authority or responsibility to choose or determine the members of a team.
-
C.
teamFrom
chosen
Indicates that one entity is the team or organization from which another entity originates, is associated, or belongs.
-
D.
teamUpWith
Indicates forming a cooperative partnership or alliance with another entity to work together toward a shared goal.
-
E.
managedTeamFrom
Indicates that one entity led, directed, or supervised a team originating from or based in another specified 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.