Triple
T19070103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby sevens |
E466768
|
entity |
| Predicate | teamSizeVariantOf |
P134173
|
FINISHED |
| Object | 15-a-side rugby union |
—
|
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: 15-a-side rugby union | Statement: [Rugby sevens, teamSizeVariantOf, 15-a-side rugby union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamSizeVariantOf Context triple: [Rugby sevens, teamSizeVariantOf, 15-a-side rugby union]
-
A.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
-
B.
team
Indicates that multiple entities are grouped together as a collaborative unit working toward shared goals or tasks.
-
C.
teamUpWith
Indicates forming a cooperative partnership or alliance with another entity to work together toward a shared goal.
-
D.
collaborationSize
Indicates the number of participants involved together in a given collaborative relationship or activity.
-
E.
teamConstraint
Indicates a rule or limitation governing how entities can be grouped, associated, or operate together as a team.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19ea01c8190b9bb789da32f9a90 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:03 p.m.