Triple
T1014594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laniakea Supercluster |
E21901
|
entity |
| Predicate | cosmicWebRole |
P20395
|
FINISHED |
| Object | node in large-scale structure |
—
|
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: node in large-scale structure | Statement: [Laniakea Supercluster, cosmicWebRole, node in large-scale structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicWebRole Context triple: [Laniakea Supercluster, cosmicWebRole, node in large-scale structure]
-
A.
cosmicForm
Indicates a relationship where an entity manifests, assumes, or is represented in a vast, universal, or transcendent cosmic form.
-
B.
cosmicFunction
chosen
Indicates a relationship where an entity serves a fundamental or overarching role within a cosmic or universal system.
-
C.
roleInGalaxy
Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
-
D.
cosmicFamily
Indicates a familial or kinship relationship that exists at a cosmic or universal scale between entities.
-
E.
galacticComponent
Indicates that one entity is a structural part or subregion of a galaxy, such as a disk, bulge, halo, or similar galactic subdivision.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7be907c8190b5c6ea89257755a7 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b72207c08190a3dbb2aa7acbbc71 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.