Triple
T10608658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | original 13 rules of basketball |
E275943
|
entity |
| Predicate | dribblingMentioned |
P94916
|
FINISHED |
| Object | no |
—
|
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 | Statement: [original 13 rules of basketball, dribblingMentioned, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dribblingMentioned Context triple: [original 13 rules of basketball, dribblingMentioned, no]
-
A.
mentions
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
B.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
C.
eraMentioned
Indicates that a specific historical or temporal era is explicitly referenced or mentioned in a given context.
-
D.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
-
E.
mentionsRiver
Indicates that an entity refers to or brings up a river in some form of content or communication.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4d0a6881909fea20378085173d |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 7:32 p.m.