Triple
T22412808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3C 84 |
E554033
|
entity |
| Predicate | createsStructure |
P64053
|
FINISHED |
| Object | X-ray cavities in the Perseus Cluster gas |
—
|
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: X-ray cavities in the Perseus Cluster gas | Statement: [3C 84, createsStructure, X-ray cavities in the Perseus Cluster gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsStructure Context triple: [3C 84, createsStructure, X-ray cavities in the Perseus Cluster gas]
-
A.
producesStructure
chosen
Indicates that one entity generates, forms, or creates a physical or conceptual structure as a result of its action or function.
-
B.
spawnStructure
Indicates that an entity causes a new structure to be created or instantiated in the environment.
-
C.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
D.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
-
E.
plannedStructure
Indicates that one entity is a structure that is intended or designed to be built or established in the future, rather than already existing.
- 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1594496348190ba25dc0193d092f2 |
completed | April 29, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.