Triple
T32364942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tap In |
E826964
|
entity |
| Predicate | useSampleOf |
P118139
|
FINISHED |
| Object | Blow the Whistle |
—
|
NE NERFINISHED |
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: Blow the Whistle | Statement: [Tap In, useSampleOf, Blow the Whistle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useSampleOf Context triple: [Tap In, useSampleOf, Blow the Whistle]
-
A.
usesSamplingOf
Indicates that one entity employs or relies on a sample or subset derived from another entity for its operation, analysis, or processing.
-
B.
basedOnSampleOf
Indicates that something is derived, inferred, or constructed from a particular sample or subset of data rather than from the entire population.
-
C.
sampleUsage
Indicates that an entity is used as an example or illustration to demonstrate how something works or is applied.
-
D.
usesSampleOfSpeechBy
Indicates that one entity employs or incorporates a sample of speech produced by another entity.
-
E.
featuresSamplesFrom
chosen
Indicates that one entity includes or incorporates sample elements originating from another entity.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 12:50 a.m.