Triple
T4758482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rugby sevens |
E105644
|
entity |
| Predicate | lineoutPlayersPerTeam |
P58325
|
FINISHED |
| Object | 2 to 4 |
—
|
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: 2 to 4 | Statement: [rugby sevens, lineoutPlayersPerTeam, 2 to 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineoutPlayersPerTeam Context triple: [rugby sevens, lineoutPlayersPerTeam, 2 to 4]
-
A.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
B.
playersPerSideOnField
Indicates the number of players from each team that are simultaneously present on the field during play.
-
C.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
-
D.
numberOfPlayersOnIcePerTeam
Indicates the count of players from a single team who are on the ice at the same time during play.
-
E.
maximumScoringRunnersPerTeam
Indicates the maximum number of runners on a team who can be counted or considered based on their scoring performance.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650c11f4819098cd1f490f711dc8 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:20 p.m.