Triple
T22400707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perseus Cluster |
E553749
|
entity |
| Predicate | hasBeenUsedFor |
P98
|
FINISHED |
| Object | studies of intracluster medium physics |
—
|
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: studies of intracluster medium physics | Statement: [Perseus Cluster, hasBeenUsedFor, studies of intracluster medium physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenUsedFor Context triple: [Perseus Cluster, hasBeenUsedFor, studies of intracluster medium physics]
-
A.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
B.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
C.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
-
D.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b39c908190a735aa860d733869 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.