Triple
T18956865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6712 |
E463801
|
entity |
| Predicate | tidalTailsDetected |
P22854
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NGC 6712, tidalTailsDetected, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tidalTailsDetected Context triple: [NGC 6712, tidalTailsDetected, true]
-
A.
isTidalInteractionSuspected
Indicates that a gravitational interaction between astronomical bodies is suspected to be causing observable tidal effects or disturbances.
-
B.
tidalDebris
chosen
Indicates material that has been gravitationally stripped from an astronomical object and dispersed into space by tidal forces.
-
C.
tidalInteraction
Indicates that two astronomical bodies exert mutual tidal forces that exchange angular momentum and energy, altering their rotations and orbits over time.
-
D.
tidalRadius
Indicates the characteristic distance from a massive object at which its tidal forces dominate and can disrupt or strip material from another bound system.
-
E.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5cdf2d08190a0aecd3fa5335a75 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon