Triple
T18569078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Test Team Rankings |
E453830
|
entity |
| Predicate | includesTeamType |
P132579
|
FINISHED |
| Object | full member national teams |
—
|
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: full member national teams | Statement: [ICC Test Team Rankings, includesTeamType, full member national teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTeamType Context triple: [ICC Test Team Rankings, includesTeamType, full member national teams]
-
A.
includesTeam
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
B.
includesInvitedTeams
Indicates that certain teams are explicitly included as invited participants in an event, activity, or context.
-
C.
alsoIncludesTeamsFrom
Indicates that something not only includes its primary elements but additionally encompasses teams originating from another specified group, category, or source.
-
D.
includesGuestTeams
Indicates that an entity contains or involves one or more teams designated as guests within its scope or composition.
-
E.
isTeamSpecific
Indicates that something applies only to, or is restricted to, a particular team rather than being general or shared across multiple teams.
- F. None of above. chosen
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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b0075a08190a5d590d36089ca1e |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:43 a.m.