Triple
T8691008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic 10 women's volleyball |
E206286
|
entity |
| Predicate | teamLimitOnCourt |
P39852
|
FINISHED |
| Object | 6 players per side |
—
|
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: 6 players per side | Statement: [Atlantic 10 women's volleyball, teamLimitOnCourt, 6 players per side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamLimitOnCourt Context triple: [Atlantic 10 women's volleyball, teamLimitOnCourt, 6 players per side]
-
A.
teamRosterLimit
Indicates the maximum number of members that are allowed to be on a team’s roster.
-
B.
playersPerMatch
Indicates the number of players that participate in a single match.
-
C.
playersPerSideOnField
chosen
Indicates the number of players from each team that are simultaneously present on the field during play.
-
D.
teamLimitPerAssociation
Indicates the maximum number of teams that can be associated with a single association or grouping.
-
E.
foulLimitPerTeam
Indicates the maximum number of fouls that a single team is allowed to commit within a defined game or competition context.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5735ffdc819094126e2698f98511 |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.