Triple
T19335640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division II Women’s Golf Championship |
E483614
|
entity |
| Predicate | teamSizeFormat |
P135466
|
FINISHED |
| Object | collegiate team scoring plus individual medalist |
—
|
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: collegiate team scoring plus individual medalist | Statement: [NCAA Division II Women’s Golf Championship, teamSizeFormat, collegiate team scoring plus individual medalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamSizeFormat Context triple: [NCAA Division II Women’s Golf Championship, teamSizeFormat, collegiate team scoring plus individual medalist]
-
A.
teamSizeVariantOf
Indicates that one entity represents a variation of another entity specifically in terms of team size configuration or composition.
-
B.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
-
C.
rosterSize
Indicates the total number of individuals included on a given roster.
-
D.
teamCountType
Indicates how the number of teams is categorized or measured within a given context.
-
E.
staffSize
Indicates the number of staff members associated with an entity.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61644b80c819080f9bca086424a36 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:33 p.m.