Triple
T14559213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenny from the Block |
E341622
|
entity |
| Predicate | usesSampling |
P91539
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Jenny from the Block, usesSampling, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSampling Context triple: [Jenny from the Block, usesSampling, Yes]
-
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.
usesSamplingOrInterpolation
chosen
Indicates that one entity applies sampling or interpolation techniques to obtain or approximate values from another entity or dataset.
-
C.
hasBeenSampledIn
Indicates that an entity has been selected or taken as a sample within a specified context, location, or dataset.
-
D.
basedOnSampleOf
Indicates that something is derived, inferred, or constructed from a particular sample or subset of data rather than from the entire population.
-
E.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3881b788190922932fb8ff81160 |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.