Triple
T14837274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molten basketball |
E348863
|
entity |
| Predicate | usedInCategory |
P40744
|
FINISHED |
| Object | men's professional basketball |
—
|
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: men's professional basketball | Statement: [Molten basketball, usedInCategory, men's professional basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCategory Context triple: [Molten basketball, usedInCategory, men's professional basketball]
-
A.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
usedInCatalogue
Indicates that something is included or referenced as an entry within a catalogue.
-
C.
categoryIUsedFor
chosen
Indicates that one entity is used as a category or classification label for another entity.
-
D.
classificationUsedBy
Indicates that a particular classification system or scheme is employed or applied by a given entity.
-
E.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded28d0ddc8190a34e3e2d469ab762 |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:52 a.m.