Triple
T22698139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M66 Group |
E561240
|
entity |
| Predicate | interactionCauses |
P694
|
FINISHED |
| Object | distorted spiral arms in Messier 66 |
—
|
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: distorted spiral arms in Messier 66 | Statement: [M66 Group, interactionCauses, distorted spiral arms in Messier 66]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionCauses Context triple: [M66 Group, interactionCauses, distorted spiral arms in Messier 66]
-
A.
interactionBetween
Indicates a reciprocal or mutual action, influence, or communication occurring between two or more entities.
-
B.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
-
C.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
causeInStory
Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
-
E.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178a008448190b393335704128fe8 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:14 p.m.