Triple
T12430538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 7320 |
E297016
|
entity |
| Predicate | belongsToClusterOrGroup |
P12263
|
FINISHED |
| Object | Local Supercluster vicinity |
—
|
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: Local Supercluster vicinity | Statement: [NGC 7320, belongsToClusterOrGroup, Local Supercluster vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToClusterOrGroup Context triple: [NGC 7320, belongsToClusterOrGroup, Local Supercluster vicinity]
-
A.
belongsToGroup
chosen
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
B.
associatedWithCluster
Indicates that an entity is linked or grouped with a particular cluster, typically sharing common characteristics or membership within that cluster.
-
C.
memberOfGroupWith
Indicates that an entity belongs to, or is associated as a member with, a particular group or collection of entities.
-
D.
belongsToDivision
Indicates that an entity is a member of, or is organizationally assigned to, a specific division.
-
E.
belongsToAgency
Indicates that an entity is under the authority, control, or affiliation of a specific agency.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.