Triple
T25433529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayles |
E637318
|
entity |
| Predicate | playStructure |
P29019
|
FINISHED |
| Object | normal play convention |
—
|
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: normal play convention | Statement: [Kayles, playStructure, normal play convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playStructure Context triple: [Kayles, playStructure, normal play convention]
-
A.
danceStructure
Indicates a structural or organizational relationship between elements within a dance, such as how movements, sections, or patterns are arranged and connected.
-
B.
raceStructure
Indicates a structural or organizational relationship that defines how a race (such as a competition or contest) is arranged, configured, or composed.
-
C.
actStructure
Indicates a structural or organizational relationship that defines how an action or activity is arranged, composed, or internally organized.
-
D.
eventStructure
Indicates how an event is internally organized into components such as subevents, phases, participants’ roles, and their temporal or causal relationships.
-
E.
playType
chosen
Indicates the specific category or style of play or performance associated with an event or action.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6dd99f88190848a5bbee795aa17 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:59 p.m.