Triple
T4898870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA women’s golf |
E109747
|
entity |
| Predicate | scoringFormatCommon |
P48244
|
FINISHED |
| Object | stroke play |
—
|
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: stroke play | Statement: [NCAA women’s golf, scoringFormatCommon, stroke play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoringFormatCommon Context triple: [NCAA women’s golf, scoringFormatCommon, stroke play]
-
A.
scoringType
chosen
Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
-
B.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
C.
scoringUnit
Indicates that one entity functions as a unit or component responsible for scoring or assigning scores to another entity.
-
D.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
E.
primaryScoringStyle
Indicates the main method or approach by which an entity achieves or generates scores or points.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:28 p.m.