Triple
T4555785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaqtin’ A Fool |
E120472
|
entity |
| Predicate | hasSegmentFrequency |
P18808
|
FINISHED |
| Object | weekly during NBA season |
—
|
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: weekly during NBA season | Statement: [Shaqtin’ A Fool, hasSegmentFrequency, weekly during NBA season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSegmentFrequency Context triple: [Shaqtin’ A Fool, hasSegmentFrequency, weekly during NBA season]
-
A.
hasFrequencyCategory
Indicates that something is associated with a particular classification of how often it occurs or is used.
-
B.
hasMultipleSegments
Indicates that the referenced entity is composed of more than one distinct segment or section.
-
C.
hasFrequencyNote
chosen
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
-
D.
hasSegmentOn
Indicates that one entity includes or occupies a specific segment or portion on another entity (such as a line, path, or sequence).
-
E.
hasColorSegments
Indicates that an entity is composed of or divided into distinct parts, each associated with a specific color.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5813af948190b10b02dadf6496bf |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.