Triple
T1014591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laniakea Supercluster |
E21901
|
entity |
| Predicate | galaxyFlowDirection |
P19752
|
FINISHED |
| Object | toward Great Attractor |
—
|
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: toward Great Attractor | Statement: [Laniakea Supercluster, galaxyFlowDirection, toward Great Attractor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: galaxyFlowDirection Context triple: [Laniakea Supercluster, galaxyFlowDirection, toward Great Attractor]
-
A.
dataFlowDirection
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
B.
drainageDirection
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
C.
flowsGenerallyDirection
chosen
Indicates that something typically moves or progresses in a particular overall direction, without requiring an exact or constant path.
-
D.
galacticDestination
Indicates that one entity serves as the target or endpoint location within a galaxy that another entity is directed or traveling toward.
-
E.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
- 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.