Triple
T19915428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Place Where You Go to Listen |
E478652
|
entity |
| Predicate | computesFrom |
P82730
|
FINISHED |
| Object | seismological sensors |
—
|
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: seismological sensors | Statement: [The Place Where You Go to Listen, computesFrom, seismological sensors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computesFrom Context triple: [The Place Where You Go to Listen, computesFrom, seismological sensors]
-
A.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
-
B.
isUsedToCompute
Indicates that one entity serves as an input, basis, or resource for performing a calculation or deriving a result about another entity.
-
C.
computationInput
chosen
Indicates that an entity serves as input data or parameters consumed by a computation or processing activity.
-
D.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
E.
targetComputation
Indicates a relationship where one computation is designated or identified as the specific goal, focus, or intended result among possible computations.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6599394f081909246006c2e83bacc |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.