Triple
T36508623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 British and Irish Lions tour to South Africa |
E899836
|
entity |
| Predicate | includesTeamFrom |
P29737
|
FINISHED |
| Object | England |
E1791
|
NE 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 | Statement: [1980 British and Irish Lions tour to South Africa, includesTeamFrom, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTeamFrom Context triple: [1980 British and Irish Lions tour to South Africa, includesTeamFrom, England]
-
A.
includesTeam
chosen
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
B.
includesTeamsThat
Indicates that an entity contains or encompasses specific teams as part of its composition or scope.
-
C.
includesTeamType
Indicates that an entity encompasses or is associated with one or more specific categories or types of teams.
-
D.
alsoIncludesTeamsFrom
Indicates that something not only includes its primary elements but additionally encompasses teams originating from another specified group, category, or source.
-
E.
includesInvitedTeams
Indicates that certain teams are explicitly included as invited participants in an event, activity, or context.
- F. None of above.
Provenance (4 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbbaa4d881909b642bb261e41e3f |
completed | June 23, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.