Triple
T25433555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayles |
E637318
|
entity |
| Predicate | hasPlayConvention |
P165816
|
FINISHED |
| Object | no passing allowed |
—
|
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: no passing allowed | Statement: [Kayles, hasPlayConvention, no passing allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayConvention Context triple: [Kayles, hasPlayConvention, no passing allowed]
-
A.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
-
B.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
C.
isTypicallyPlayed
Indicates that an activity, game, or sport is commonly engaged in or performed by a particular type of participant or group.
-
D.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
E.
hasPlayFormat
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 21, 2026, 1:59 p.m.