Triple
T10608652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | original 13 rules of basketball |
E275943
|
entity |
| Predicate | originalEquipment |
P94915
|
FINISHED |
| Object | soccer ball |
—
|
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: soccer ball | Statement: [original 13 rules of basketball, originalEquipment, soccer ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalEquipment Context triple: [original 13 rules of basketball, originalEquipment, soccer ball]
-
A.
standardEquipmentOrigin
Indicates that an item’s standard equipment comes from or is originally supplied by a specified source or origin.
-
B.
originallyBuilt
Indicates that one entity was the first or initial builder or constructor of another entity.
-
C.
primaryEquipment
Indicates that one entity serves as the main or most important piece of equipment used by another entity.
-
D.
originallyBuiltUnder
Indicates that something was first constructed during the rule, authority, or administration of a particular person, group, or regime.
-
E.
originallyBuiltBy
Indicates that something was first constructed or created by a particular agent, organization, or entity.
- 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.