Triple
T6106473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan Golf Tour |
E136127
|
entity |
| Predicate | primaryPlayingFormat |
P29019
|
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: [Japan Golf Tour, primaryPlayingFormat, stroke play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPlayingFormat Context triple: [Japan Golf Tour, primaryPlayingFormat, stroke play]
-
A.
televisionFormat
Indicates the specific type or style of television program or production format associated with an entity.
-
B.
projectionFormat
Indicates the specific technical format or method used to project visual content (such as film or digital media) onto a display surface.
-
C.
playType
chosen
Indicates the specific category or style of play or performance associated with an event or action.
-
D.
typicalBroadcastFormat
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
-
E.
primaryPlayerSource
Indicates that an entity serves as the main origin or provider of a player within a given context or system.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b806bd48190b6f020af3391adb8 |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.